MCP client and server
Understanding the Model Context Protocol in Boki
MCP client and server
Boki can act as both an MCP client and an MCP server. This page explains what that means and why it matters.
What is MCP?
MCP — Model Context Protocol — is a standard for connecting AI agents to external tools and data. It lets agents access capabilities beyond their built-in features.
Think of it like an API for AI agents. Instead of building integrations from scratch, tools expose an MCP interface that any MCP-compatible agent can use.
Boki as MCP client
When Boki acts as an MCP client, it connects to external MCP servers to access their tools.
Example: Connecting to the Ahrefs MCP server gives Boki's agents access to SEO data, keyword research, and backlink analysis.
Why use Boki as MCP client?
- Extend agent capabilities: Give Boki agents access to tools you already use
- Unified workflow: Access external data without leaving Boki
- Contextual research: Agents can pull relevant data while helping you
Connecting MCP servers
- Go to Settings → Agents
- Add the MCP server URL, name, and credentials
- Boki agents can now use that server's tools
Boki as MCP server
When Boki acts as an MCP server, external clients can connect to Boki to access your content.
Endpoint: https://app.boki.io/api/mcp
Why use Boki as MCP server?
- Access Boki from other tools: Use Claude Desktop, Cursor, or other MCP clients to read and write Boki content
- Automation: Build workflows that interact with Boki programmatically
- Integration: Connect Boki to your broader tool ecosystem
Available tools
Boki's MCP server exposes approximately 48 tools across these scopes:
- Articles (read/write)
- Briefs (read/write)
- Plans (read/write)
- Social posts (read/write)
- Distributions (read/write)
- Short links (read/write)
- Experts (read/write)
- Insights (read/write)
- Components (read/write)
- Workspace context
Authentication
Access requires a personal access token (PAT):
- Generate a token in Settings → Agents → MCP tokens
- Token format:
boki_pat_xxxxxxxxxxxx - Tokens expire after 30 days
- Configure your MCP client with the URL and token
See How to generate an MCP token.
Client vs server comparison
| Role | Boki connects to... | External tools connect to... |
|---|---|---|
| Client | External MCP servers | — |
| Server | — | Boki's MCP endpoint |
You can use both simultaneously:
- Boki as client: Agents access Ahrefs, other MCP servers
- Boki as server: Claude Desktop accesses your Boki content
Security considerations
As client
- Only connect MCP servers you trust
- Credentials are stored securely
- You control which servers Boki can access
As server
- Tokens are shown once — store them securely
- Revoke tokens you no longer use
- Each token authenticates as you — guard accordingly
Related
- How to add an MCP server — Client setup
- How to generate an MCP token — Server setup
- MCP tokens reference — Technical specification