Copilot Studio vs Salt
A side-by-side look at the Copilot Studio and Salt MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Copilot StudioConversational AI · Local subprocess (stdio)MCP bridge for Copilot Studio sign-in, environment selection, and Agentic Builder access.59GoodAuth: oauth 2.0Verdict: choose Copilot Studio for conversational ai work as a local process; choose Salt for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Copilot Studio when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
discover_resources, get_consumption, manage_agents.
Choose Salt when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
create_salt_agent, list_salt_agents, delegate_to_agent.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Copilot Studio | |
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 59/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 5 | 32 |
| Full listing | View Copilot Studio | View Salt |
Tools & capabilities
Copilot Studio tools 5
discover_resourcesDiscover connector operations and schemas, existing connections, dependent parameter values, and attachable resources.get_consumptionRead historical agent or workflow credit consumption, or current environment credit capacity.manage_agentsManage agent inventory, complete draft authoring, lifecycle, published-agent sharing, saved-draft previews, and agent evaluation suites and runs.manage_workflowsManage workflow inventory, complete draft authoring, lifecycle, real tests, and run diagnostics.get_copilot_studio_skillsStart here for Copilot Studio guidance. Read the matching core skill before authoring, then read `schema.json`.
Salt tools 32
create_salt_agentdisplay_name`, `username`, `description`, `personalist_salt_agentsnonedelegate_to_agenttarget_agent_id`, `taskreport_progressstatus`, `titleconsult_agenthandle`, `questionrequest_floornonepost_cardblocks`, `chat_idupdate_cardcard_id`, `blockscreate_productname`, `kind`, `pricelist_productsnoneoffer_productproduct_idsend_invoiceline_items- +20 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Copilot Studio
{
"mcpServers": {
"copilot-studio": {
"command": "npx",
"args": [
"-y",
"@microsoft/copilot-studio-mcp@latest"
]
}
}
}
Salt
{
"mcpServers": {
"salt": {
"command": "npx",
"args": [
"-y",
"salt-mcp"
]
}
}
}
Frequently asked questions
Copilot Studio is categorized under Conversational AI and uses a local stdio subprocess. Salt belongs to Conversational AI and uses a local stdio subprocess. Pick Copilot Studio for conversational ai work and Salt for conversational ai.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Copilot Studio has no declared pricing — check the project's own site. Auth: oauth 2.0. Salt has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add copilot-studio and salt as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Copilot Studio has a quality signal of 59/100 (Good) with 0 views, 0 installs and 3 GitHub stars. Salt has 55/100 (Good) with 1 views, 0 installs and 1 GitHub stars.