Connect Pipefy to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Pipefy, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Pipefy + Microsoft Copilot

Pipefy work management platform: organizations, pipes (workflows), cards and phases through the GraphQL API. List the pipes an AI assistant can see, track cards as they move through phases, and read card field values.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

PIPEFY_API_TOKEN

Step 1 — Get credentials

Setting up takes a few minutes. You need a Pipefy account and an API token.

1. Open https://app.pipefy.com/tokens, click Generate new token, give it a description and save. Use the longer token shown there. For production, Pipefy recommends a Service Account token instead (see the Authentication page in the Pipefy developer docs).
2. Paste the token into PIPEFY_API_TOKEN. The connector sends it as a bearer token on every call.
3. Install the connector and run pipefy_list_organizations: it lists the organizations the token can see and doubles as the check that the token works.

What it reads: your organizations, the pipes (workflows) of an organization, and one pipe with its card counts, phases, start-form fields and labels. It lists the cards of a pipe with title, done flag, update time, current phase and assignees, opens one card with every field value, and shows one phase with its card count and fields. A typical path is pipefy_list_organizations, pipefy_list_pipes, pipefy_get_pipe (to learn the phase ids), pipefy_list_cards and pipefy_get_card.

Ids: all Pipefy ids are numbers. A pipe id is the number in the pipe URL, e.g. 301234567 in https://app.pipefy.com/pipes/301234567, and card, phase and organization ids work the same way.

Limits: pipefy_list_cards returns 25 cards per page by default and at most 50, the most Pipefy returns per request. When pageInfo.hasNextPage is true, the AI passes pageInfo.endCursor as after to get the next page. Pipefy also has a monthly API-call quota that depends on your plan, and one tool call is one API call.

The connector is read-only: it does not create, move or update cards, and it does not search cards (it pages through them instead).

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Pipefy tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT