Menu
Browse documentation

Connect Canvas Perch to Claude Desktop

Use Claude's remote custom-connector flow with a public HTTPS Canvas Perch MCP endpoint and OAuth consent.

Follow the steps

  1. Use a deployed Canvas Perch MCP URL such as https://YOUR_DEPLOYED_API_ORIGIN/mcp. It must be reachable from the public internet over HTTPS.

  2. In Claude Desktop, open Customize → Connectors, choose Add custom connector, and enter the exact Canvas Perch MCP URL.

  3. Complete the OAuth sign-in and approve only the Canvas Perch scopes the conversation needs. Keep library:write out unless capture_note is intentional.

  4. Enable the connector for the conversation, review the available tools, and revoke the connection from Claude's connector controls or Canvas Perch Settings → Connections when finished.

Choose only the access you need

Personal keys always expire: the default is 90 days and the maximum is 365 days. Choose a non-empty subset of the available scopes and revoke the key when the connection is finished.

Personal API key scopes
ScopeWhat it allowsMCP tools
boards:writeCapture selected web content to editable canvases. Also requires library:write.REST capture endpoint; no additional MCP tool
boards:readList and read canvases the account can view.list_canvases, read_canvas
library:readList and search the account’s own library.search_library
library:writeCreate, update and delete library items through REST.capture_note

Code examples

Replace placeholders in your own protected environment. Never paste a real key into a public page, browser bundle, prompt, screenshot, issue or repository.

Remote connector URL
https://YOUR_DEPLOYED_API_ORIGIN/mcp

What to know

  • Anthropic's remote connector flow calls the remote server from Anthropic's cloud infrastructure, including when the user is operating Claude Desktop. A private localhost, VPN-only, or firewalled API is not a valid remote connector target.
  • The current server does not ship the local .mcpb/stdio path documented separately by Anthropic. Do not use a claude_desktop_config.json recipe for Canvas Perch until a tested local extension exists.
  • A personal bearer key is supported by the Canvas Perch protocol, but the Claude Desktop custom-connector UI guide should lead with OAuth until a pasted-key path is verified for that client.

Troubleshooting

  • If Claude cannot reach the server, check public HTTPS reachability, the exact /mcp path, and the reverse proxy's forwarded headers.
  • If OAuth returns a resource or redirect error, restart from the connector flow and preserve the exact advertised resource URL and redirect values.
  • If a write tool appears unexpectedly, disconnect and reconnect with a grant that omits library:write, or revoke the grant in Canvas Perch Settings → Connections.
  • If you need localhost access, wait for a separately shipped and tested local extension; the current remote connector path cannot reach a developer's localhost.

Official references

External client details were checked against these first-party sources.

Need a hand with the next step?

Browse the other guides or send us the details of where you got stuck.

Contact Canvas Perch