Connect Chit Chats to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Chit Chats, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Chit Chats + Microsoft Copilot

Let your AI handle Chit Chats shipping: create shipments, compare postage rates, print labels, group parcels in batches for drop-off, track deliveries and see returns. Buying postage and refunds stay off until you allow them.

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:

CHIT_CHATS_ACCESS_TOKEN, CHIT_CHATS_CLIENT_ID

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Chit Chats account: an API access token from its settings and the client ID from the address of your dashboard.

1. Sign in at chitchats.com and open Settings, Account (chitchats.com/settings/account). Create an API access token and copy it into CHIT_CHATS_ACCESS_TOKEN. Paste the token only: it is sent as the raw Authorization header, without a Bearer prefix.
2. Copy your client ID into CHIT_CHATS_CLIENT_ID. It is the number in the address of your Chit Chats dashboard, https://chitchats.com/clients/<client id>/..., for example 999999.
3. Install the connector and run chit_chats_list_shipments to check the connection.

Cloud and self-hosted work the same way: the connector calls chitchats.com with your own token from either, and there is nothing else to set up. Deleting the token in Chit Chats revokes access at once.

Nothing is charged until you buy postage: chit_chats_create_shipment with postage_type set to unknown creates a shipment without postage, and chit_chats_get_shipment then shows the eligible rates with their prices. chit_chats_refresh_shipment updates stale rates or changes insurance, signature and ship date. Creating shipments, refreshing rates and batching charge nothing. Destinations outside Canada and the US need customs line items.

Buying postage runs in the background: after chit_chats_buy_postage the shipment status is postage_requested; read it again until it is ready or postage_purchase_failed. A ready shipment carries its label as PNG and ZPL links (postage_label_png_url, postage_label_zpl_url): the connector returns links, not files.

Batches for drop-off: a batch groups the packages you drop off together and has its own label. Create one with chit_chats_create_batch, add shipments with chit_chats_add_shipments_to_batch (or take them out with chit_chats_remove_shipments_from_batch) and print the batch label from chit_chats_get_batch.

Ids, amounts and paging: a shipment id is 10 letters and digits (8ERNJ8SCQ9); a batch id is a number. Amounts are decimal strings in the currency of the account, and dates are YYYY-MM-DD. List tools take limit (default 100, at most 1000) and page; a page shorter than limit is the last.

Rate limit: Chit Chats allows 2000 requests per 5 minutes per IP address and account and answers 429 beyond that. Wait for the seconds in the Retry-After header and try again.

Common errors: 401 means Chit Chats refused the access token: create a new one under Settings, Account and paste it without the word Bearer. 403 means the token does not belong to this client ID: check the number in your dashboard address. 404 means there is no client, shipment or batch with that id: check CHIT_CHATS_CLIENT_ID and take shipment ids from chit_chats_list_shipments.

Live account only: the Chit Chats staging sandbox (staging.chitchats.com) needs a separate account and is not used by this connector. Account balance, invoices and pickup scheduling are not part of the public API.

What it reads: shipments with their status, recipient address, contents, declared value, package size and weight, postage type, carrier and carrier tracking code, ship date, the amounts charged, label links, the eligible postage rates with prices, and tracking events; the number of shipments and batches; batches with their status and drop-off label; returns coming back to you, with status and resolution; and the public tracking of any recent Chit Chats shipment, with estimated delivery and every event with time and location.

Switched off at install: chit_chats_buy_postage, chit_chats_refund_shipment, chit_chats_delete_shipment and chit_chats_delete_batch. Buying postage charges your Chit Chats account balance; a refund voids the shipment, so it can no longer be shipped; deleting removes a pending shipment (no postage yet) or an empty batch for good. Switch on only the ones you need on the connector page; the AI asks you to confirm every change first, and before every purchase the shipment, rate and price. Creating and refreshing shipments, creating batches and moving shipments in and out of them are switched on: they charge nothing.

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 Chit Chats 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

Example prompts

• "Which shipments are still pending without postage, and which are ready to drop off?"
• "Create a shipment for order 1042 to the address below and compare the postage rates before buying anything."
• "Put all ready shipments into a new batch and give me the batch label to print."
• "Where is shipment 8ERNJ8SCQ9 now, and when should it arrive?"
• "Show me the returns on hold that are waiting for me to choose a return method."

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