Skip to main content

Core Features

MCP Tool Integrations

Expand your Portal One AI agents' capabilities! Learn to connect them to external tools, APIs, and data sources with MCP Tool Integration. Unlock advanced automation and integrate seamlessly.

Learn how to connect your Portal One agents to external tools, APIs, and data sources using the Model Context Protocol (MCP) to vastly expand their capabilities.

Prerequisites:

Unlock Your Agent's Potential with MCP Tool Integration

Portal One agents are powerful, but imagine if they could directly interact with your company's database, pull real-time stock data, manage your GitHub repositories, or even control other parts of your Portal One workspace. That's where the Model Context Protocol (MCP) comes in.

MCP is an open standard that acts like a universal adapter, giving your Portal One agents a standardized way to securely connect to and use external tools, data sources, and services. Unlike traditional one-off API integrations requiring custom development, MCP provides a standardized, plug-and-play approach, drastically simplifying the process. Instead of being limited to internal knowledge, agents can leverage MCP to perform real-world actions, transforming them from smart assistants into truly capable automated workers.

Think of it like giving your agent specialized equipment – access to a specific database, a connection to a particular web service, or tools to manage files – allowing them to perform tasks far beyond simple conversation or text generation.

Why Use MCP Integration in Portal One?

Integrating MCP servers unlocks several key advantages:

  • Vastly Expanded Capabilities: Connect agents to thousands of potential tools and services, from public APIs (like weather or news) to private company databases or internal software.
  • Real-Time Data Access: Allow agents to fetch and use up-to-the-minute information from external sources.
  • Automation Beyond Portal One: Enable agents to perform actions in other systems (e.g., create a ticket in your project management tool, update a record in your CRM).
  • Leverage Specialized Tools: Connect agents to specialized external AI models or data processing services.
  • Standardized & Secure: MCP provides a consistent, secure way for agents to interact with tools, often replacing the need for complex, custom-coded integrations.

Use Cases for MCP Integration

The possibilities are vast, but here are a few examples:

  • Workspace Management with the Portal One MCP Server: Portal One provides its own MCP server. An administrative agent can leverage this server to automatically manage workspace resources. For instance, a Portal One agent can use tools from this server to automatically create new specialized agents, modify or add memories to agents, manage forms and conversation state, and more.
  • Customer Service: An agent could use an MCP tool connected to your company's order database (via an MCP server you host) to look up a customer's order status directly within a support conversation.
  • Content Creation: A research agent could use an MCP tool linked to a Google News or scientific journal API (via a public or private MCP server) to gather the latest articles or data for summarizing into a report.
  • Development Workflows: An agent connected to a GitHub MCP server could list open pull requests or even create new issues based on user instructions.
  • Data Entry: An agent could take information from a conversation and use an MCP tool to save structured data into an external database or spreadsheet via a custom MCP server.

How to Connect an MCP Server in Portal One

Connecting your Portal One workspace to an MCP server is straightforward:

  1. Navigate to MCP: In the left-hand navigation menu of your Portal One workspace, click on "MCP".
  2. Initiate Connection: Click the "+ Connect" button, usually located near the top right of the MCP Integration page.
    • Namespace: Enter a unique, descriptive name for this server connection (e.g., internal_crm, google_news_api, github_tools). This helps you identify the tools later and prevents naming conflicts if multiple servers offer tools with the same name (like search).
    • Server URL: Paste the full URL of the MCP server you want to connect to, making sure to include the full endpoint (usually ends with /mcp or /sse).
  3. Connect: Click the "Connect" button in the dialog.

Provide Server Details: A dialog box will appear.

Dialog box titled "Connect to MCP Server" with input fields for "Namespace" (example: "Google News") and "Server URL" (example: "https://mcp.server.com/api"). A "Connect" button is visible.
Clicking the "Connect" button will open this dialog. Fill in the Namespace and the Server URL fields and press "Connect".

The server connection will now appear in the list on the MCP Integration page. You can click on it to expand its details.

Portal One's MCP Integration page showing an expanded "portal" MCP server. Details include the server URL, a "Custom Headers" section with an "x-api-key" example, a table listing tools like "portal_add_service" with their success rate and description, and "Sync" and "Delete" buttons below the table.
Expanded view of a connected MCP Server in Portal One, showing its details, custom headers, available tools, and management options.

Configuring Authentication and Syncing Tools

Once connected, you will likely need to configure authentication and then sync the tools.

Authentication Methods

When connecting MCP servers, you typically authenticate through one of these methods:

  • Custom Headers: Expand the server details view. In the "Custom Headers" section, click "+ Add Header" to input required headers. For example: x-api-key with the value YOUR_ACTUAL_API_KEY.
  • OAuth Authentication: If the server uses OAuth, an "Authenticate" button will appear in the server details view. Clicking this will guide you through the server's specific OAuth flow.
  • URL Token: Some servers may require embedding an authentication token directly into the Server URL as a query parameter. For example: https://mcp.example.com/sse?token=YOUR_SECURE_TOKEN.

Always consult the documentation for the specific MCP server to understand its required authentication method.

Syncing and Testing Tools

  • Syncing Tools: After connecting (and authenticating, if necessary), click the "Sync" button within the expanded server details view. Portal One will communicate with the MCP server to fetch the list of available tools, their descriptions, and input schemas. This list will then populate the table in the details view.
  • Testing Tools: You can use the "Run" button next to each tool in the list to test it directly from the Portal One interface (you may need to provide sample inputs). This helps verify the connection and understand what the tool does.
  • Periodic Syncing: It's good practice to re-sync periodically, especially if the MCP server's tools might be updated by its provider.

Assigning MCP Tools to Your Agents

Connecting an MCP server makes its tools available to your workspace, but you need to explicitly grant individual agents permission to use them:

  1. Navigate to Agent Config: Go to "Agents", select the agent you want to empower, and click on its "Config" tab.
  2. Find Tools Section: Scroll down to the "Tools and integrations" card.
  3. Select Tools: Choose the specific MCP tools you want this agent to be able to use. They will appear listed in the "Tools and integrations" card.

Assigning tools selectively helps ensure your agent only accesses relevant capabilities, enhancing security and efficiency by limiting exposure to unnecessary resources and focusing the agent on its designated tasks.

Portal One Agent Configuration screen, focusing on the "Tools and integrations" card. Assigned tools like "portal_list_agents" and "portal_get_agent" are listed with an 'x' to remove them. A "+ Connect Tools" button is visible.
Assigning specific MCP tools to an agent within its "Tools and integrations" configuration.

How Agents Use MCP Tools

Once an agent has been assigned MCP tools:

  • Automatic Use: The agent's underlying LLM will "see" the available tools (including their names and descriptions provided by the MCP server) and can choose to use them when it deems appropriate during a conversation or task to fulfill a user's request.
  • Explicit Instructions: For more complex tasks or to ensure a specific tool is used, you might need to provide explicit instructions to the agent, either in its core "Memory" or directly within a conversation prompt. For example: "Use the internal_crm__lookup_customer tool to find the email address for customer ID 12345."
  • Tool Quality Matters: The likelihood of an agent successfully using a tool depends on the LLM, the clarity of the tool's name and description (provided by the MCP server), and the tool's historical success rate (visible in the MCP Integration UI).

Finding and Choosing MCP Servers

A growing ecosystem of MCP servers is available:

  • Public Registries: Explore marketplaces and lists like mcpmarket.com, mcp.so, smithery.ai, glama.ai, or community aggregations like the awesome-mcp-servers list on GitHub.
  • Private/Custom Servers: You can connect to MCP servers hosted by your own company or even run them on your own infrastructure for maximum control and security when accessing internal resources. Follow the server provider's documentation to get the necessary URL and authentication details.

Important Considerations

  • Namespacing: Use clear, unique namespaces when connecting servers to avoid confusion between tools with similar names.
  • Authentication: Carefully configure the required authentication based on the MCP server's requirements. Always keep API keys and tokens secure and never share them publicly.
  • Error Handling & Troubleshooting: If an agent tries to use an MCP tool and fails, the error message returned by the tool/server will typically be inserted directly into the conversation history. This allows the agent (or you) to see what went wrong and potentially adapt the plan. The success/failure rate is also tracked per tool in the MCP Integration UI, helping you identify unreliable tools. If you notice frequent tool errors, review the tool's definition for clarity (as provided by the MCP server), or try explicitly instructing your agent on tool usage. Persistent errors may require troubleshooting the MCP server itself or contacting the MCP server developer.
  • Security Best Practices: Exercise caution when connecting to third-party MCP servers. Always verify third-party MCP servers' sources and code before integration. Wherever possible, prefer running MCP servers on your own infrastructure or trusted hosting environments. Prioritize using servers where you can verify the code (e.g., open-source servers you run yourself) or trust the provider. Always use robust authentication methods. Avoid exposing sensitive internal systems without proper security measures on the MCP server itself.
  • Syncing: Remember to "Sync" the server connection in Portal One if the underlying tools on the MCP server are changed or updated by its provider.

Conclusion

MCP Tool Integration is a powerful feature that dramatically extends the reach and capabilities of your Portal One agents. By connecting to external tools and services through standardized MCP servers, you can automate more complex workflows, leverage real-time data, and build agents that interact meaningfully with the systems and data sources crucial to your operations. Start exploring the available MCP servers or consider building your own to truly unlock your agents' potential.