--- title: "Build an MCP Connector for AI Agents | Paperclip" description: "Build an MCP connector for Paperclip agents. Learn about connection types and permissions, start with the authoring runbook and coordinate your contribution in Discord." canonical: https://paperclip.ing/product/connectors/build/ source_commit: 569c7203aa24b95440682983ce7940ba1d4247bd source_checked: 2026-10-03 copy_sha256: 85b63ef927aba5ccdbe724d82da6ad5124149c7b16f3b83880f51aa0a258b8e5 prompt_sha256: 548f107a764d9368dbf1a1dfdca812263f405f5aa351bba6b9865541797c3be7 section_c_source_commit: 0fe47882cfcb12082035113c59ca96091c46ebfc section_c_revision: 17757852-59c6-4024-a987-064e6ffdc6af section_c_sha256: c0d5f4b2cbbf07b2e7ff07d018cfd15279f256507ac3e40cfd76957fc0af420d --- # Build a connector for your product [Read the connector runbook](https://github.com/paperclipai/paperclip/blob/master/doc/connections/CONNECTOR-PLAYBOOK.md) [Questions? Ask in Discord](https://discord.gg/m4HZY7xNG3) ## Choose how your product works with agents Give agents a way to use your product. Each company decides who can use the connection. ### Types - **Agent tool:** Agents call your product’s actions while they work. - **Chat:** People message agents from inside your product. - **Model provider:** Agents use your models through an AI connection in supported runtimes. ### Permissions - **Tool actions:** Companies set each action to Allowed (runs right away), Ask first (waits in Review for a person’s OK) or Off (won’t run). - **Agent access:** Companies choose which agents can use the connection. - **Account identity:** Tool connections can act for the company, one person or one dedicated agent. - **Provider access:** Request only the documented scopes your actions need. Paperclip can’t expand an issued key’s permissions. ## How it works 1. Build your connector with the [connector runbook](https://github.com/paperclipai/paperclip/blob/master/doc/connections/CONNECTOR-PLAYBOOK.md). 2. Join #dev on our [Discord](https://discord.gg/m4HZY7xNG3) for community questions and help, or email support@paperclip.ing. 3. Then open a pull request with your connector. Our maintainers will review it and work with you to get it merged. Add your product name, customer workflow and developer docs. ```text We are the team behind [PRODUCT NAME]. Help us prepare a Paperclip connector for this customer workflow: [CUSTOMER WORKFLOW]. Official developer documentation: [DOCS URL]. Provider server or API documentation, if separate: [SERVER OR API DOCS URL]. First read the current Paperclip Connection Authoring Runbook: https://github.com/paperclipai/paperclip/blob/master/doc/connections/CONNECTOR-PLAYBOOK.md Also read CONTRIBUTING.md, ROADMAP.md, AGENTS.md and the background documents required by the runbook. Record the repository commit you inspect. Search for an existing connector and duplicate or related pull requests. Preserve unrelated worktree changes. Start with a bounded plan: the customer workflow, proposed actions, supported connection method, required account access, missing prerequisites and acceptance checks. Do not assume a catalog entry proves runtime support. Use our official provider documentation and current protocol metadata. Verify authentication, scopes, account or plan requirements, limits and action risks. Reuse an official remote server where supported. If an API needs a wrapper or execution adapter, explain that work before implementation. Do not invent capabilities or assume writes start disabled. After we authorize the implementation plan, follow the runbook in order. Use the existing AppDefinition contract and generation pipeline. Add runtime code only when the existing contract cannot represent the integration. Use official artwork with provenance. Keep credentials in approved secret references. Preserve Paperclip's access controls, action policies and audit boundaries. Document setup, supported actions, account access, restrictions, revocation and maintenance responsibilities. Use a concrete action-based tagline. Derive any safety warning from this provider's own documentation. Identify service involvement as required by the runbook. Do not claim a partnership, approval or official availability. After building with the runbook, ask us whether we have questions or need community help in Discord. Prepare questions for us to share when needed. Do not contact anyone on our behalf. Run the smallest relevant deterministic tests first, then the runbook's PR-ready checks. Record exact commands and results. Ask us for test-account authorization before live proof and for authorization before any live write. Check setup, tool discovery, an allowed read, a governed write where supported and authorized, a denied/quarantined call when the method declares one, refresh or reconnect, revocation and audit evidence. Keep secrets out of logs and artifacts. Mark checks not run as unverified; do not treat mocks as live provider proof. Deliver the implementation, setup documentation, official artwork and provenance, claim/source notes, test evidence and maintenance notes. Read the current .github/PULL_REQUEST_TEMPLATE.md immediately before drafting the PR body. Fill every section truthfully, including linked public issues or an issue description, verification, risks and the model used. Include duplicate or related PRs. All tests and required CI checks must pass, and the PR needs a 5/5 Greptile score with comments addressed before merge. Prepare a draft PR body and review checklist for us. Do not open a PR, merge, deploy, publish, send messages, change global policy defaults or perform risky actions without our authorization. Maintainers may close uncoordinated feature PRs. Neither this prompt nor passing checks guarantees acceptance, publication or a delivery date. Begin with the plan and questions that block it. ``` ## Start with one useful customer workflow. [Read the connector runbook](https://github.com/paperclipai/paperclip/blob/master/doc/connections/CONNECTOR-PLAYBOOK.md) [Questions? Ask in Discord](https://discord.gg/m4HZY7xNG3)