feat(swarms): add Swarms third-party MCP plugin

[kyegomez]

Adds Swarms as a third-party MCP plugin — the Swarms API for multi-agent orchestration, packaged from Swarms' hosted remote MCP server.

What it does

Points at Swarms' official hosted Streamable HTTP endpoint, https://mcp.swarms.world/mcp. Nothing to install and nothing to run locally. It exposes 23 tools:

Category	Tools
Agents	Single agent completions, parallel agent batches, list agent configurations
Swarms	Multi-agent swarm completions across 14 architectures (SequentialWorkflow, ConcurrentWorkflow, HierarchicalSwarm, MixtureOfAgents, GroupChat, MajorityVoting, AgentRearrange, MultiAgentRouter, CouncilAsAJudge, LLMCouncil, DebateWithJudge, HeavySwarm, RoundRobin, PlannerWorkerSwarm), swarm batches, architecture discovery
Specialized workflows	Graph workflows, batched grid workflows, reasoning agents and their types, auto agent builder
Models and tools	Available models, OpenAI-compatible model list and chat completions, available API tools
Account and monitoring	Rate limits, credit balance, pricing, metrics summary, request logs, premium endpoints, health

Auth

A user-supplied Swarms API key sent as an x-api-key header, declared through variables so Cursor prompts for it on install — the only thing a user configures.

{
  "mcpServers": {
    "swarms": {
      "type": "http",
      "url": "https://mcp.swarms.world/mcp",
      "headers": {
        "x-api-key": "${SWARMS_API_KEY}"
      }
    }
  }
}

The server holds no key of its own; it forwards the caller's key upstream to https://api.swarms.world. The credential stays on the transport and is never a tool argument, so the model driving the tools never sees it. Keys come from https://swarms.world/platform/api-keys.

This matches Swarms' own documented Cursor setup: https://docs.swarms.ai/docs/documentation/clients/swarms-api-mcp

Verification

• node scripts/validate-plugins.mjs → All plugins validated successfully.
• initialize against the live endpoint returns protocol 2025-06-18, server swarms_api 1.0.0.
• tools/list returns 23 tools without credentials, as documented.
• tools/call without a key returns a tool-level error (isError: true) instructing the caller to send x-api-key, not a transport failure.
• tools/call with a key returns HTTP 200 OK — GET /v1/swarms/available plus the architecture list.

Files

• third_party/swarms/ — plugin.json, mcp.json, README.md, CHANGELOG.md, LICENSE, assets/logo.png (192×192, Swarms' official mark from the The-Swarm-Corporation GitHub organization)
• Registered in .cursor-plugin/marketplace.json and the root README.md table

Docs: https://docs.swarms.ai

---

Note

Low Risk
Additive marketplace plugin with no core repo logic changes; user API keys stay in plugin configuration and calls are delegated to Swarms’ hosted MCP.

Overview
Adds Swarms as a new third-party Cursor plugin and registers it in .cursor-plugin/marketplace.json and the root README.md integrations table.

The new third_party/swarms/ package follows the usual MCP plugin layout: manifest (plugin.json with required SWARMS_API_KEY), mcp.json pointing at Swarms’ hosted HTTP MCP at https://mcp.swarms.world/mcp with x-api-key auth, plus README, CHANGELOG, LICENSE, and logo assets. No local server code—chat agents reach Swarms’ remote tools (agents, multi-agent swarms, workflows, models, account/usage) through that endpoint.

^{Reviewed by Cursor Bugbot for commit 0dd6b87. Bugbot is set up for automated code reviews on this repo. Configure here.}