Connectors & MCP

What is MCP?

Model Context Protocol (MCP) is an open standard by Anthropic that lets any application expose its capabilities as tools — callable functions with typed inputs and outputs.

WCP uses MCP as its connector protocol. Any app with an MCP server becomes a WCP connector with zero custom code.

ConnectorHub

The ConnectorHub manages the lifecycle of MCP processes:

• Lazy startup: MCP processes start on first use and are reused for the session
• Process isolation: each connector runs as a separate process (stdio transport)
• Auto-shutdown: processes are terminated when WCP shuts down

Registering a Connector

Any MCP server can be registered. The only requirement is a command that starts the server:

{
  "name": "obsidian",
  "command": "npx",
  "args": ["-y", "mcp-obsidian"],
  "env": {
    "OBSIDIAN_VAULT": "/Users/me/vault"
  }
}

Capability Classification

After registration, run /api/capabilities/scan. WCP:

1. Starts the MCP process
2. Calls tools/list to get all available tools
3. Classifies each tool as read, write, or list based on name patterns and schema analysis
4. Stores the classifications as CapabilityBindings

Classification rules

Pattern	Direction
get_*, read_*, fetch_*, query_*	read
create_*, write_*, update_*, set_*, upsert_*	write
list_*, search_*	list

Known Compatible MCP Servers

App	Package	Notes
Notion	mcp-notion-server	Pages, databases
Google Drive/Sheets	@modelcontextprotocol/server-gdrive	Files, sheets
Obsidian	mcp-obsidian	Notes, vault
GitHub	@modelcontextprotocol/server-github	Issues, PRs, files
Filesystem	@modelcontextprotocol/server-filesystem	Local files
PostgreSQL	@modelcontextprotocol/server-postgres	Queries, writes
Slack	@modelcontextprotocol/server-slack	Messages, channels

Any MCP server in the MCP registry works.