MCP Server

SCM can run as an MCP (Model Context Protocol) server, allowing AI assistants to access your context directly.

Running the MCP Server

scm mcp serve

This starts SCM as an MCP server over stdio.

Claude Code Configuration

Add SCM to ~/.claude/settings.json:

{
  "mcpServers": {
    "scm": {
      "command": "/path/to/scm",
      "args": ["mcp", "serve"]
    }
  }
}

Replace /path/to/scm with your actual binary location (e.g., ~/go/bin/scm).

Auto-Registration

By default, SCM auto-registers itself as an MCP server. Control this with:

scm mcp auto-register --disable
scm mcp auto-register --enable

Or in config:

mcp:
  auto_register_scm: false

Available MCP Tools

Context Tools

Tool	Description
list_fragments	List fragments with optional filtering
get_fragment	Get specific fragment content
list_profiles	List all profiles
get_profile	Get profile configuration
assemble_context	Combine fragments, profiles, tags
list_prompts	List all prompts
get_prompt	Get prompt content
search_content	Search across all content types

Management Tools

Tool	Description
create_profile	Create new profile
update_profile	Modify existing profile
delete_profile	Remove profile
create_fragment	Create new fragment
delete_fragment	Remove fragment
apply_hooks	Apply hooks to backend configs

Remote Tools

Tool	Description
list_remotes	List configured remotes
add_remote	Register new remote
remove_remote	Unregister remote
discover_remotes	Search GitHub/GitLab for SCM repos
browse_remote	List items in remote
preview_remote	Preview content before pulling
confirm_pull	Install previewed item

MCP Server Tools

Tool	Description
list_mcp_servers	List configured servers
add_mcp_server	Add server config
remove_mcp_server	Remove server
set_mcp_auto_register	Toggle auto-registration

Sync Tools

Tool	Description
sync_dependencies	Sync remote dependencies
lock_dependencies	Generate lockfile
install_dependencies	Install from lockfile
check_outdated	Check for updates
check_missing_dependencies	Find missing deps

Tool Schemas

assemble_context

{
  "profile": "string",
  "bundles": ["string"],
  "tags": ["string"]
}

list_fragments

{
  "query": "string",
  "tags": ["string"],
  "sort_by": "name|source",
  "sort_order": "asc|desc"
}

search_content

{
  "query": "string (required)",
  "types": ["fragment", "prompt", "profile", "mcp_server"],
  "tags": ["string"],
  "sort_by": "name|type|relevance",
  "sort_order": "asc|desc",
  "limit": "integer"
}

create_profile

{
  "name": "string (required)",
  "description": "string",
  "parents": ["string"],
  "bundles": ["string"],
  "tags": ["string"],
  "default": "boolean"
}

update_profile

{
  "name": "string (required)",
  "description": "string",
  "add_parents": ["string"],
  "remove_parents": ["string"],
  "add_bundles": ["string"],
  "remove_bundles": ["string"],
  "add_tags": ["string"],
  "remove_tags": ["string"],
  "default": "boolean"
}

add_mcp_server

{
  "name": "string (required)",
  "command": "string (required)",
  "args": ["string"],
  "backend": "unified|claude-code|gemini"
}

sync_dependencies

{
  "profiles": ["string"],
  "force": "boolean",
  "lock": "boolean",
  "apply_hooks": "boolean"
}

MCP Usage Examples

Within an AI assistant conversation:

> assemble context with the developer profile

● scm - assemble_context (MCP)(profile: "developer")
  ⎿ { "context": "# Development Standards\n..." }

> search for python content

● scm - search_content (MCP)(query: "python", types: ["fragment"])
  ⎿ { "results": [...], "count": 5 }

> list available remotes

● scm - list_remotes (MCP)()
  ⎿ { "remotes": [{"name": "scm-main", ...}] }

Managing MCP Servers

SCM can manage MCP server configurations:

scm mcp list
scm mcp add tree-sitter -c "npx" -a "tree-sitter-mcp"
scm mcp add my-server -c "/path/to/server" -b claude-code
scm mcp remove tree-sitter
scm mcp show tree-sitter

Bundle MCP Definitions

Bundles can include MCP server definitions:

mcp:
  tree-sitter:
    command: "tree-sitter-mcp"
    args: ["--stdio"]
    notes: "AST parsing for code"
    installation: "npm install -g tree-sitter-mcp"

  database:
    command: "postgres-mcp"
    args: ["--connection", "localhost:5432"]
    env:
      PGPASSWORD: "${PGPASSWORD}"

These MCP servers are registered when the bundle is used.

Security Considerations

warning

MCP servers can execute arbitrary commands with user permissions. Only install servers from trusted sources.

When pulling from remotes:

• MCP Servers: Can execute arbitrary commands
• Context Items: Risk of prompt injection
• Bundles: Combine both risks

Always review content before installing with scm fragment install.