Skip to content
Maypop Docs

MCP from the command line

maypop mcp manages the same integrations as Integrations in your settings, plus tools for testing them.

Connect a server

Section titled “Connect a server”

Pass secrets through environment variables, never as literal arguments, so they don’t end up in your shell history:

Terminal window
export SEARCH_MCP_AUTH="Bearer ..."
maypop mcp connect search https://mcp.example.com \
  --header-env Authorization=SEARCH_MCP_AUTH
maypop mcp list

Maypop checks the server answers before saving it, and stores its credentials encrypted. Services that sign in with OAuth are connected from Integrations in your settings; the CLI can then list and link them.

Section titled “Link it to your app”

Inside a repository connected with maypop init:

Terminal window
maypop mcp link search      # give this app access
maypop mcp linked           # what this app can use
maypop mcp unlink search

Inspect and try tools

Section titled “Inspect and try tools”
Terminal window
maypop mcp tools search             # readable list
maypop mcp tools search --json      # raw schemas, for scripts and agents
maypop mcp call search web_search --arguments '{"query":"Maypop SDK"}'

Add --app to go through the app’s link rather than your personal connection — the way your app will reach it. call takes one JSON object matching the tool’s input schema, prints the raw MCP result, and exits with an error when the tool reports one, so it works as a check in scripts.

Tools can change things in the external service: read a tool’s description before calling it.

maypop mcp disconnect search removes the connection and all its app links.