Skip to main content
Section navigation

MCP Servers

Connect and manage Model Context Protocol (MCP) servers on systemprompt.io. MCP servers provide tools and resources to your AI agents.

On this page

MCP servers are the bridge between Claude and the outside world. On systemprompt.io, MCP servers give Claude access to your skills, agents, plugins, and data -- turning it from a general-purpose assistant into a purpose-built automation platform.

What is the Model Context Protocol?

The Model Context Protocol (MCP) is an open standard that defines how AI models communicate with external systems. Instead of relying solely on what a model already knows, MCP lets Claude reach out to servers that provide:

Capability What it does Example
Tools Actions Claude can perform Create a task, send a message, query a database
Resources Data Claude can read Your project files, knowledge bases, configuration
Prompts Reusable instruction templates A code review checklist, a meeting summary format

MCP follows a client-server architecture. Claude acts as the client, and MCP servers expose capabilities that Claude can discover and use during a conversation.

The Skill Manager: Your Built-in MCP Server

systemprompt.io includes a built-in MCP server called the Skill Manager. This is the primary way Claude interacts with your workspace. You do not need to install or run anything locally -- the Skill Manager runs as a remote MCP server hosted on systemprompt.io.

When Claude connects to the Skill Manager, it gains access to everything you have configured in your workspace:

  • Skills you have created or installed from the marketplace
  • Agents with their specific instructions and capabilities
  • Plugins that extend what your agents can do
  • Content and resources stored in your workspace

The Skill Manager endpoint is:

https://systemprompt.io/api/v1/mcp/skill-manager/mcp

Claude connects to this endpoint and automatically discovers all the tools and resources available in your workspace. When you add a new skill or install a plugin, Claude picks it up on the next connection refresh -- no manual configuration required.

How Agents Use MCP

When you create an agent on systemprompt.io, that agent's capabilities are exposed through the Skill Manager. Here is how the flow works:

  1. You create an agent in the systemprompt.io dashboard and assign it skills and plugins.
  2. The Skill Manager registers the agent's capabilities as MCP tools.
  3. Claude connects to the Skill Manager and discovers the available tools.
  4. During a conversation, Claude calls these tools to perform actions on your behalf.

This means your agents can do things like search your knowledge base, create content, manage tasks, interact with third-party services, or run multi-step workflows -- all through natural conversation with Claude.

MCP Server Types on systemprompt.io

systemprompt.io supports two categories of MCP servers:

Built-in: Skill Manager

The Skill Manager is always available and requires no setup beyond connecting Claude to your workspace. It provides access to all platform-native capabilities including skills, agents, plugins, and content management.

Marketplace MCP Servers

The systemprompt.io marketplace offers additional MCP server configurations that extend your workspace with specialized capabilities. These are pre-configured server definitions that you can install and activate from your dashboard. Browse the marketplace to find servers for specific use cases like data analysis, content generation, or integration with external services.

Key Concepts

Tools are discoverable. Claude does not need to be told what tools exist. When it connects to the Skill Manager, it automatically receives a list of available tools with their descriptions and parameters.

Authentication is handled for you. The Skill Manager authenticates requests using your systemprompt.io account. You do not need to manage API keys or tokens for the MCP connection itself.

Tools update in real time. When you add, remove, or modify skills and plugins in your dashboard, those changes are reflected in what Claude sees the next time it refreshes its connection.

Each workspace is isolated. Your MCP server only exposes the tools and resources belonging to your workspace. Team members with access to the same workspace share the same set of capabilities.

Next Steps