Q: Connect the same MCP multiple times? How to insert files like pdf, Word and website links?
Hi Sean, As a social media marketer, I want to create AI agents that know everything about my clients to write content, among other things. I want to provide these agents with knowledge through documents, links, and possibly by connecting them to an MCP server. So agent A knows everything about client A, agent B everything about client B, and so on.
My question is: if I connect agent A to the OneDrive MCP, can I also do this for agent B, agent C, etc.? Will I then get the OneDrive message saying “AgenticFlow has already connected…”?
The same applies to e.g. the Microsoft Word MCP. I want to avoid this.
With MCP servers within AgenticFlow, I don’t need APIs from other platforms, right? Because those would mean extra subscriptions and costs.
Or do you know a better and simpler way to handle this?
SeanP_AgenticFlowAI
May 13, 2025A: Hey Mark,
Great questions about managing client-specific knowledge and MCP connections!
1. Connecting the Same MCP Multiple Times (e.g., OneDrive for different agents):
You connect an MCP service (like OneDrive) once to your AgenticFlow workspace. This creates one "MCP Server" entry in your settings.
Then, you can equip multiple different agents (Agent A, Agent B, Agent C) with that same OneDrive MCP connection.
Crucially: Within each agent's prompts or the workflows they use, you'll tell them which specific folders or files on that OneDrive account are relevant to them. Agent A will be told to look at "Client A's Folder," Agent B at "Client B's Folder," etc.
You don't get multiple "AgenticFlow has already connected" messages for OneDrive. It's one connection, used contextually by different agents.
2. MCP Servers & APIs/Subscriptions:
Using an MCP server within AgenticFlow means you're connecting to that service's API through a standardized MCP interface.
You still need an account (and potentially a paid subscription if required by the service itself) for the underlying platform (e.g., a Microsoft account for OneDrive, a Google account for Google Drive/Sheets). The MCP makes it easier to tell AgenticFlow how to use that service's API; it doesn't bypass the need for an account with the service itself.
The benefit is often avoiding direct, complex API coding within AgenticFlow and having a more natural language way for agents to use those tools.
3. Inserting Files (PDF, Word) & Website Links for Knowledge:
Direct File Upload (PDF, DOCX, TXT, MD): Yes! This is now LIVE as part of our Data section revamp. You can directly upload these file types into an Agent's Knowledge Base. This is often the simplest way for static documents. See: https://agenticflow.featurebase.app/p/support-pdf-upload-for-knowledge-base
Website Links: When creating an agent, you can paste URLs for it to crawl and learn from. You can also use web scraping nodes in workflows to feed it web content.
4. Simpler Way for Client-Specific Knowledge:
For each client:
- Create a dedicated Agent (e.g., "Client A Content Agent").
- Upload Knowledge: Directly upload their specific PDFs, Word docs, etc., into that agent's Knowledge Base using the new file upload feature.
- Web Links: Add their key website pages as knowledge sources for that agent.
- OneDrive/Shared Drive (Optional): If they have a shared OneDrive folder you both access, connect your OneDrive MCP once to the workspace. Then, in "Client A Content Agent's" prompts, tell it to reference files only from "Client A's specific folder" on that OneDrive.
This way, each agent has its own curated knowledge specific to that client.
Hope this makes it clearer!
— Sean