Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hypha-docs.plinqx.app/llms.txt

Use this file to discover all available pages before exploring further.

MCP Servers let you connect external Model Context Protocol (MCP) servers to Plinqx, federating their tools alongside your other tool sources.

​
What are MCP Servers?

MCP Servers are external services that implement the MCP protocol. By connecting them to Plinqx, you can:
  • Federate Tools: Access tools from multiple MCP servers through one gateway
  • Unified Access: Use tools from different servers with a single API key
  • Centralized Governance: Apply policies to all tools regardless of source

​
Adding an MCP Server

1

Navigate to Connections

Click Connections or MCP Servers in the sidebar.
2

Add Connection

Click Add Connection and select External MCP Server.
3

Configure Connection

Provide:
  • Name: Descriptive name for this connection
  • Provider: Select “External MCP Server”
  • Server URL: The MCP server endpoint
  • Authentication: Configure how to authenticate with the server
4

Discover Tools

Plinqx automatically discovers available tools from the MCP server.

​
Authentication

MCP servers may require authentication. Common methods:
  • None: Public MCP servers
  • API Key: Simple key-based auth
  • Bearer Token: OAuth2 or JWT tokens
  • Custom: Server-specific authentication
Store authentication credentials in the Vault and reference them using {{vault.CREDENTIAL_NAME}}.

​
Tool Discovery

Once connected, Plinqx automatically:
  1. Discovers all tools exposed by the MCP server
  2. Imports tool definitions (name, description, input schema)
  3. Makes tools available for addition to Collections

​
Managing Connections

​
Connection Status

Monitor connection health:
  • Active: Connected and tools available
  • Error: Connection issue - check URL and authentication
  • Refreshing: Discovering tools

​
Refreshing Tools

If the MCP server adds new tools:
  1. Open the connection details
  2. Click Refresh Tools
  3. New tools are automatically discovered

​
Removing Connections

To disconnect an MCP server:
Removing a connection removes all its tools from Collections. Remove tools from Collections first if needed.
  1. Open the connection
  2. Click Delete Connection
  3. Confirm removal

​
Example: Composio Integration

Composio is a popular MCP server that provides integrations with many services.
1

Get Composio Credentials

Sign up for Composio and get your API key.
2

Create Vault Entry

Store the Composio API key in the Vault.
3

Add Connection

Add Composio as an External MCP Server with:
  • Server URL: Composio’s MCP endpoint
  • Authentication: API Key using your Vault entry
4

Discover Tools

Composio tools are automatically discovered and available.

​
Best Practices

Use Vault

Store all MCP server credentials in the Vault

Monitor Status

Regularly check connection status for reliability

Test Tools

Test MCP server tools in the Playground before production

Document Sources

Use clear connection names to identify tool sources

​
Next Steps

Add to Collections

Add MCP server tools to collections

Set Up Vault

Store MCP server credentials securely