Stumpy
Persistent AI agents that run 24/7 in your Slack, Telegram, SMS, or email
← Back to Docs
The MCP plugin lets your agent connect to external MCP servers, giving it access to tools and capabilities beyond what Stumpy provides built-in. If a service offers an MCP server, your agent can use it.
What It Does
MCP (Model Context Protocol) is a standard for connecting AI agents to external tools. With MCP enabled, your agent can connect to any MCP-compatible server and use the tools it provides.
For example, you might connect your agent to:
- A company's internal API exposed as an MCP server
- A specialized data service
- Custom tools you've built for your own workflow
- Third-party services that offer MCP endpoints
Enabling
- Go to your agent's page and click "+ Add Plugin" in the sidebar
- Find MCP and click Enable
Adding an MCP Server
On the MCP plugin page:
- Enter a name for the server (for your reference)
- Enter the server URL (the MCP endpoint)
- Choose the authentication method: None, API Key (with optional custom header and prefix), or OAuth
- Click Add Your agent immediately gains access to all tools provided by that server. You can connect to multiple MCP servers.
How Your Agent Uses External Tools
Once connected, the tools from external servers appear alongside your agent's built-in tools. Your agent uses them automatically based on what you ask.
For example, if you connect an MCP server that provides a "query_database" tool, you can ask your agent "look up the latest sales figures" and it will use that tool to fetch the data.
You do not need to tell your agent which tools to use. It sees the available tools and their descriptions and chooses the right one for the task.
MCP Servers vs. MCP Setup
These are two different things:
MCP Servers (this page) lets your agent connect to external MCP servers to use their tools. Your agent is the client, calling out to other servers.
MCP Setup lets you manage your Stumpy agents from MCP clients like Claude Code, Claude Desktop, or ChatGPT. You are the client, managing your agents from external tools.
They can be used together. Your agent can consume tools from external servers, and you can manage your agents from MCP clients.
Limitations
- The external MCP server must be accessible via HTTP
- Server credentials are encrypted before storage
- Tool availability depends on the external server being online and responsive
- Your agent trusts the tools provided by connected servers, so only connect to servers you trust
Servidores relacionados
tip.md x402 + CDP
An MCP server for the tip.md platform that enables AI agents to facilitate crypto tipping using x402 payment collection and CDP automatic disbursement.
Taiwan-Health-MCP
A Model Context Protocol (MCP) server exposing Taiwan healthcare datasets such as ICD-10 and drug information for AI agents.
Tripletex MCP Server
MCP server for Tripletex — Norwegian ERP and accounting platform. Invoices, customers, employees, projects, and ledger entries.
BuyWhere MCP
Real-time product search across Southeast Asia with 3.8M+ items — the first SEA e-commerce MCP server
RuneScape
Interact with RuneScape (RS) and Old School RuneScape (OSRS) data, including item prices and player hiscores.
Smart Home Device Control
Control smart home devices and query information by connecting large models to smart home backend APIs.
Nexbid
Agentic commerce infrastructure for AI agents. MCP-native product discovery, contextual ad matching, and purchase facilitation with European privacy compliance (nDSG/GDPR).
relate2-narratives
Agent-native narrative intelligence marketplace. 144 structured stories, 37 characters, human complexity scenarios. Pay per asset via x402 on Base Mainnet.
Kite Trading
A server for performing trading operations using the Kite Connect API.
Holvi MCP Server
MCP server for Holvi — Finnish business banking for entrepreneurs. View balances, transactions, create and send invoices via AI agents.