MCP Integration
The MCP (Model Context Protocol) server exposes Apart Intelligence as a set of tools that AI assistants can use directly. Your organizational knowledge becomes available inside Claude, Cursor, and any MCP-compatible tool — no copy-paste needed.
Setup
Quick example — add to your Claude Desktop or Cursor config:
claude_desktop_config.json / .cursor/mcp.json
{
"mcpServers": {
"apart-intelligence": {
"command": "npx",
"args": ["-y", "@apart-tech/intelligence-mcp"],
"env": {
"APART_API_URL": "https://api.intelligence.apart.tech",
"APART_API_KEY": "apart_your-api-key"
}
}
}
}
For Claude Code, install the CLI skills for the best experience:
Tip
See the
MCP Setup Guidefor detailed instructions for every supported tool — Claude Code, Cursor, VS Code, Windsurf, Codex CLI, Gemini CLI, Cline, JetBrains, and Zed — including tool-specific quirks, recommended approaches, and troubleshooting.
Available Tools
The MCP server provides 60+ tools organized by category:
Read Tools
| Tool | Description |
|---|
search_knowledge | Hybrid semantic + keyword search with workspace filtering |
get_node | Retrieve a specific node with its edges (supports PII decryption) |
get_context | Assemble a context package via search + graph traversal |
get_neighborhood | N-hop graph neighborhood of a node |
list_drafts | List nodes pending review |
list_types | Node and edge type inventory |
list_domains | Full domain taxonomy tree |
list_workspaces | All available workspaces |
get_workspace | Workspace definition with filter rules |
export_workspace | Export workspace as markdown |
Write Tools
| Tool | Description |
|---|
add_node | Create a knowledge node (defaults to draft) |
update_node | Modify an existing node |
link_nodes | Create a typed edge between two nodes |
set_status | Change lifecycle status (draft/approved/archived) |
delete_node | Delete a node and all its edges |
delete_edge | Delete an edge between two nodes |
Graph Health Tools
| Tool | Description |
|---|
health_report | Comprehensive graph health report |
validate_edges | Detect self-loops, duplicates, low-relevance connections |
find_orphans | Find nodes with no connections |
find_duplicates | Find near-duplicate nodes by embedding similarity |
find_islands | Detect disconnected clusters with optional bridge suggestions |
suggest_links | Suggest missing links between similar unconnected nodes |
analyze_relationship_types | Find semantically similar relationship types to merge |
retype_edges | Rename all edges of one type to another |
PII Tools
| Tool | Description |
|---|
get_pii_config | Get the organization's PII detection/encryption policy |
test_pii | Test text for PII detection |
Maintenance Tools
| Tool | Description |
|---|
seed_domains | Seed the default domain taxonomy |
re_embed | Re-generate embeddings for nodes |
Members
| Tool | Description |
|---|
list_members | List members of the current organization |
update_member_role | Update a member's role (owner, admin, member) |
remove_member | Remove a member from the organization |
Invites
| Tool | Description |
|---|
send_invite | Invite someone to the organization by email |
list_invites | List pending invites |
revoke_invite | Revoke a pending invite |
accept_invite | Accept an invite to join an organization |
Agents
| Tool | Description |
|---|
run_agent | Run a cloud agent task (supports built-in and custom org types) |
list_agent_types | List available agent types (built-in + custom) |
list_agent_runs | List recent agent runs (filterable by type and status) |
get_agent_run | Get details and result of a specific run |
get_agent_config | Get agent configuration |
set_agent_config | Configure agent settings (API keys, model, template) |
Custom Agent Types
| Tool | Description |
|---|
list_org_agent_types | List the org's custom agent types and built-in overrides |
create_agent_type | Create a custom agent type or override a built-in type's prompt |
update_agent_type | Update a custom agent type or override |
delete_agent_type | Delete a custom agent type or remove a built-in override |
Agent MCP Servers
| Tool | Description |
|---|
list_mcp_servers | List the org's registered MCP servers for agent sandboxes |
add_mcp_server | Register an npx-based MCP server for agents |
update_mcp_server | Update an MCP server registration |
remove_mcp_server | Remove an MCP server registration |
Org Config
| Tool | Description |
|---|
get_embedding_config | Get embedding provider configuration |
set_embedding_config | Set embedding provider (BYOK) |
delete_embedding_config | Remove embedding configuration |
set_pii_config | Set PII detection and encryption policy |
delete_pii_config | Remove PII configuration |
Using Workspaces with MCP
Both search_knowledge and get_context accept a workspaceparameter that automatically applies the workspace's domain and type filters:
// Inside Claude, the AI can call:
search_knowledge({
query: "deployment process",
workspace: "tasks-ops"
})
// Or get full context:
get_context({
query: "assignment resolution",
workspace: "tasks-engineering"
})
This ensures the AI gets role-appropriate context. An engineering workspace returns architecture docs and code. A product workspace returns feature descriptions.
Tip
When an AI tool has access to your knowledge graph via MCP, it can answer questions grounded in your actual architecture, processes, and decisions — instead of generating generic responses.
Configuration
The MCP server requires two environment variables to connect to your Apart Intelligence API:
| Variable | Description |
|---|
APART_API_URL | Your API server URL (e.g. https://api.intelligence.apart.tech) |
APART_API_KEY | Your API key (starts with apart_) |
These are passed via the env field in your MCP configuration, as shown in the setup examples above. Get your API key by running ai login with the CLI, or from the Apart Intelligence dashboard.