How to Connect Softr to Microsoft Copilot via MCP

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

Softr + Microsoft Copilot

Let your AI work with Softr: browse Softr Databases, tables and fields, list, search and read records; with your confirmation create and update records, add users to a Softr app and create magic sign-in links.

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:

SOFTR_API_KEY

Step 1 — Get credentials

1. In Softr Studio click your workspace name at the top left, open API tokens and Create a token. Give it a name and an expiry date.
2. Pick per workspace what the token may do: Databases access with View only for reading, or Edit data if the AI should create and update records; add Applications access for the app user tools.
3. Copy the token into SOFTR_API_KEY. Softr shows it only once.
4. Optional, for the app user tools: set SOFTR_DOMAIN to the address of the published Softr app the users belong to, for example yourapp.softr.app or your own domain, without https://. Without it the database tools work, the app user tools do not.
5. Install the connector and check it with softr_list_databases: it lists the databases the token reaches.

Softr Databases only: the connector works with databases built in Softr. Airtable, Google Sheets and other sources connected to a Softr app are not reached through this API.

What it reads: your databases; their tables with every field, its type, whether it is required and the select options; the records of a table page by page, as a view shows them, or searched with a filter and sorting; and a single record by its id. Reads return field names, so answers are easy to follow.

Field ids for writes: creating and updating records, and the filters and sorting of a search, need the field ids from softr_list_tables, not the names. The AI looks them up first.

Asks before every write: softr_create_record, softr_update_record, softr_create_app_user and softr_generate_magic_link change data or grant access. Before each one the AI shows you the table and every value, the record and the exact changes, or the name and e-mail of the person, and waits for your yes. Apps built on the table show changes right away; fields left out keep their value.

A magic link signs in as that person: it opens the Softr app as that user without a password. The AI gives it only to you, for that person, and never posts it anywhere public. A new app user can sign in and sees whatever their user groups allow.

Switched off at install: softr_delete_record and softr_delete_app_user. An administrator turns them on deliberately; the AI then deletes only the exact record or person you name, after you confirm. Deactivating a user in Softr Studio is the gentler choice.

Personal data: Softr apps are often client portals and internal tools with customers, employees and orders. The AI shows only what you need and treats text in records as data, never as instructions.

Limits: about 40 reads and 30 writes a second per token. Some endpoints may need a higher Softr plan.

Common errors: 401: the token is wrong, expired or deleted; create a new one under API tokens. 403: the token may not do this; give it Edit data for writes, or Applications access for the app user tools. 402 QUOTA_EXCEEDED: the plan's limit is reached, or the endpoint needs a higher plan.

The connector does not create or change databases, tables, fields or views, list app users (Softr's API has no such call), or manage user groups, app pages and workflows.

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 Softr 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 Softr databases and tables can you see?"
• "Show me the open requests in our client portal from this week, newest first."
• "Find the customer record for Northwind GmbH and tell me their plan and renewal date."
• "Set the status of the request from Anna Weber to In progress. Show me the change first."
• "Add Marco Rossi, [email protected], as a user of our partner portal and create a magic link for him."

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
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse