Plugins
Captain ships plugins so agents can search and index collections directly from their runtime. Pick the one that matches where your agent lives.
Claude Code / Cursor (MCP)
OpenClaw
The Captain MCP server exposes 19 tools to any Model Context Protocol client. Claude Code, Cursor, Windsurf, and others.
What you get
Search & collections: captain_search, captain_list_collections, captain_create_collection, captain_delete_collection, captain_list_documents, captain_delete_document, captain_wipe_documents
Indexing: captain_index_url, captain_index_youtube, captain_index_text, captain_index_file (local paths, multipart upload), captain_index_s3, captain_index_gcs, captain_index_azure, captain_index_r2
Jobs: captain_job_status, captain_cancel_job
Live project search:
captain_save. save a short note (decision, gotcha, bug repro, design constraint) to a per-project collection with a timestamped filename. Auto-creates the collection on first use.captain_find. semantic search over saved notes; timestamps are surfaced so stale notes are obvious.
Credentials
Set these once in your shell (every client reads them the same way):
Get an API key at runcaptain.com/studio.
Install. Claude Code
Add to ~/.claude.json (user scope) or a project .claude.json:
Restart Claude Code. /mcp shows captain connected.
Install. Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
Or use Settings → Tools & MCP → New MCP Server and paste the inner object.
Install. any other MCP client
Usage
Optional: agent guidance
Drop a rule file in your repo so the agent reaches for Captain automatically:
Cursor. .cursor/rules/captain.mdc:
Claude Code. add the same text to CLAUDE.md in the repo root.
Links
Feature comparison
Both plugins wrap the same Captain v2 API. results from either are indistinguishable. Pick the plugin that matches your agent runtime.