Connect Podio to Microsoft Copilot via MCP

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

Podio + Microsoft Copilot

Read one Podio app: its field definitions, a filtered page of items, and a single item. Signs in with Podio app authentication. Read-only.

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:

PODIO_APP_ID, PODIO_APP_TOKEN, PODIO_CLIENT_ID, PODIO_CLIENT_SECRET

Step 1 — Get credentials

Setting up takes about 5 minutes. You need a Podio API key (client id and secret), plus the App ID and App token of the one Podio app the AI should read.

1. Open https://podio.com/settings/api and generate an API key. Copy the client id into PODIO_CLIENT_ID and the client secret into PODIO_CLIENT_SECRET. Podio shows the secret only once.
2. Open the Podio app, then the wrench menu, then Developer. Copy the App ID into PODIO_APP_ID and the App token into PODIO_APP_TOKEN.
3. Install the connector and run podio_get_app: it signs in and returns the app's name and every field.

One app only: the four values sign the connector in as that app (Podio app authentication). The access token lasts 8 hours and the connector signs in again on its own when it expires. Other apps in the workspace stay out of reach: a call outside the app returns 403. Podio's API is public, so this works on AnythingMCP Cloud and on self-hosted instances.

What it reads: podio_get_app returns every field with its field_id, external_id, type, label, required flag and settings, such as the ids of category options. podio_filter_items lists a page of items with their field values. podio_get_item opens one item by the numeric item_id from that list (not the app_item_id). Reading an item does not mark it as viewed, so it does not clear your Podio notifications.

Filters and pages: the AI filters by a field's external_id, or by title, created_on, created_by, last_edit_on, tags, item_id, app_item_id or external_id. Category values are option ids; numbers, money and dates take a from/to range, and dates can be relative, such as -7d or +1w. Text fields cannot be filtered, except the item title through title. A page holds 20 items by default and up to 100.

Limits: Podio counts calls per API key per hour: 250 for podio_filter_items and 1,000 for other reads. Over the limit Podio answers HTTP 420 (not 429), and the AI waits before trying again.

Common errors: 400 at sign-in means the client id, client secret, App ID and App token do not belong together. 401 means Podio refused the access token: save the connector again so it signs in afresh, and recheck the four values. 403 means the call left the one app this token can read. 404 means there is no app or item with that id.

The connector does not create or edit items, read comments or files, open other apps, or sign in as a Podio user.

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 Podio 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