MCP servers overview
MCP (the Model Context Protocol ) is an open standard for exposing tools to AI systems. Connect an MCP server — your own, or a pre-built one like GitHub, Stripe, or Notion — and qRaptor discovers the tools it offers so your agents can use them alongside System and Project tools.
Servers vs. discovered tools
- A server is the connection: a URL, an authentication method, and where its tools run.
- Its tools are discovered automatically when you connect. You choose which to enable, set each one’s category, and mark risky ones for approval.
Discovered tools are namespaced by the server’s short name: mcp.{'{'}shortName{'}'}.{'{'}tool_name{'}'} — for example mcp.github.create_issue.
Where MCP lives
MCP servers live on the MCP Servers tab of the Agent Tools page (Agentic Workspace → Tools). The tab shows a count of your servers, an Add from template catalog banner, and a Your Servers grid.
Each server appears as a card showing its name, its mcp.{'{'}shortName{'}'} namespace, how many tools are enabled ({'{'}enabled{'}'}/{'{'}total{'}'} tools enabled), when it was last seen, and a status badge.
Server status
| Badge | Meaning |
|---|---|
| Connected | The server is reachable and its tools are available. |
| Disconnected | The server isn’t currently connected. |
| Error | The last connection attempt failed (see Last Error on the server). |
OAuth servers show a token-based status instead — Connected, Token Expired, Reconnect Needed, Revoked, or Not Connected. See OAuth servers.
Authentication methods
When you add a server manually, you choose how qRaptor authenticates to it:
| Method | Use |
|---|---|
| None | Public server, no auth. |
| API Key | A key sent in a named header. |
| Bearer Token | A token sent as Authorization: Bearer …. |
| Custom Headers | One or more custom header name/value pairs. |
Pre-built templates may instead use OAuth2, which you connect through a redirect flow — see OAuth servers.
Execution location
Each server declares where its tools run:
| Location | Meaning |
|---|---|
| Auto (Platform decides) | The platform picks. |
| Local (Platform) | Runs on qRaptor infrastructure. |
| Remote (Executor) | Runs on one of your registered executors — use this for servers only reachable from your own infrastructure. |
Once discovered and enabled, MCP tools behave like any other tool — they appear in the Tools Call node picker and can be attached to AI Agents.
What’s next
- Add an MCP server → — the connect wizard
- OAuth servers → — the OAuth2 flow
- Manage a server → — tools, refresh, edit, delete