Skip to content
wirebase
Product · Connectors

Plug your tools into AI.

Connectors turn any service into a tool the model can call. Connect once. Use everywhere.

Connector list

Hundreds of community connectors

GitHubLinearSlackPostgresSentryNotionVercelStripeZendesk
terminal
# Add a connector in one command
$ wirebase mcp add github --url https://api.githubcopilot.com/mcp

# Or via API
$ curl -X POST https://api.wirebase.com/v1/mcp/servers \
    -H "Authorization: Bearer $WIREBASE_KEY" \
    -d '{"name": "github", "url": "https://api.githubcopilot.com/mcp"}'

# Tools auto-discover and become @-mentionable
> @github list my open PRs
Open standard

Built on MCP. Talks to anything.

Connectors are powered by the Model Context Protocol (MCP), the open standard from Anthropic that gives AI models a uniform way to call external services — from GitHub and Slack to your internal databases. Hundreds of community-built MCP servers are already available, and every one of them works as a connector out of the box over SSE or Streamable HTTP. OAuth flow handling is built in, so authenticated integrations work without any custom glue code.

  • Powered by MCP, the open standard from Anthropic
  • Hundreds of community-built servers work out of the box
  • SSE and Streamable HTTP transports supported
  • OAuth flow handling built in
Connector transport types
Custom connectors

Build once. Reuse forever.

Add a connector through the UI or via POST /api/mcp/server, and its tools are immediately available to every chat and agent in your organization. Write per-tool custom instructions to tell the model exactly how and when to use each capability — the same instructions apply whether the tool is called from a workflow, an agent, or a raw chat. Tools are auto-namespaced so there's no collision between connectors.

  • Add connectors via UI or POST /api/mcp/server
  • Per-tool custom instructions for the model
  • Per-connector scoping by org or by agent
  • Tools auto-discovered and namespaced
Adding a connector
Governed

Visibility you can trust.

Every connector tool call is rendered inline in the conversation with the arguments sent and the result returned — you always see exactly what the model did. Disable any tool per-organization from the admin panel without touching the connector configuration. Each invocation is captured in the audit log so your security team has a full record.

  • Every tool call rendered in the conversation
  • See arguments and results inline
  • Disable per-tool per-org if needed
  • Audit log captures every invocation
Tool call visibility
What's inside

Production-ready MCP host.

Transport agnostic

SSE and Streamable HTTP.

OAuth ready

Token flow built in for OAuth-protected connectors.

Per-org scope

Connectors scoped to organizations.

Custom instructions

Per-tool and per-connector hints to the model.

Audit logging

Every tool call captured.

Auto discovery

Tools appear in @-mention immediately after install.

Get your team on one AI platform.