Plugins

MCP server plugins — what your agents can do

An MCP server (Model Context Protocol — an open standard for plugging tools into agents) gives your agents a set of tools they didn't have before. Attach one from the catalog and your agents gain its capabilities the moment it's wired — no deploy, no code.

The catalog includes 48 connector rows for the systems small and medium businesses actually run on:

• Billing & finance — Stripe, QuickBooks, Plaid, Alpaca
• CRM & sales — HubSpot, Salesforce, Clay
• Docs & knowledge — Notion, Google Drive, Atlassian (Jira + Confluence), Box, Supabase
• Issues & engineering — Linear, Sentry, Figma, Asana, Monday.com
• Signing — DocuSign
• Commerce, publishing, and social — Shopify, WordPress, Ghost, Buffer, Bluesky, X, LinkedIn, Meta, Snapchat
• Renewables — Enphase, SolarEdge, PVWatts, utility-rate lookup

…plus vertical-specific connectors for the tools particular industries depend on — field-service, legal practice management, fitness and wellness scheduling, property management, payroll, restaurant operations, and more.

If a connector requires an API key, OAuth grant, or shared org credential, GroundPound blocks activation until that credential is attached and pauses the connector if the credential is later cleared. That keeps missing-credential failures visible at setup time instead of surfacing as broken agent runs.

Tool names are namespaced by server, so two servers that both offer a "create issue" tool never collide. You can attach the curated catalog entries, or point an agent at your own MCP server URL.

Skill packs — how your agents do it

GroundPound currently ships 90 skill packs. A skill pack is your house style, in plain markdown: voice and tone, escalation rules, the format a deliverable has to ship in, the way your company writes an email. Skill packs are stitched into an agent's instructions in scope order — org-wide rules first, then team, then the individual agent — so broad guidance applies everywhere and specific guidance wins where it matters.

MCP servers (strictly type mcp_server in the catalog) give an agentexternal application integration capabilities (tools for Stripe, Notion, CRMs, etc.). Skill Packs (native curated + plugin-sourced from the marketplace) give it judgment, style, and task plans. MCP sources focus exclusively on interacting with external apps. Plugin-sourced skills are Skill Pack content (not MCP) and are surfaced under Knowledge → Skill Packs.

Attach at any level, inherit down

MCP servers attach at org/team/agent scope (via Settings → Tools → MCP Sources). Skill Packs attach similarly but are managed under Settings → Knowledge → Skill Packs (native ones + plugin-sourced ones are clearly distinguished). Inheritance stacks; specific wins.

Plugins are free across all plans.

Related: see Integrations for the channels and knowledge sources your agents connect to, and the Technical configuration overview for how scopes and inheritance work.