Log inSubmit server
Workbench logo

Workbench

Self-hosted MCP aggregator exposing 194 tools from 16 integrations through nine stable meta-tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Workbench

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for workbench, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

The workbench MCP server consolidates 194 tools from 16 integrations behind nine meta-tools and one MCP endpoint. It stores separate per-user OAuth connections, encrypts tokens at rest, and injects credentials when calling provider APIs such as Jira, GitHub, Slack, and Google. Agents connect through JSON-RPC at `/mcp`, while scripts and cron jobs can use a plain JSON REST endpoint. Reach for workbench when one stable tool surface and centralized self-hosted credential management are preferable to configuring many provider-specific MCP servers.

Use cases

  • Centralize multiple SaaS integrations behind one MCP endpoint
  • Give each user separate OAuth connections to providers
  • Run integration actions from scripts or cron jobs over REST
  • Keep an agent’s tool list stable as providers change
  • Add organization-specific integrations through plugins

Key features

  • 194 tools across 16 integrations
  • Nine fixed MCP meta-tools
  • Per-user, per-provider OAuth connections
  • Encrypted token storage
  • MCP and plain JSON REST interfaces
  • SQLite or PostgreSQL storage

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
Last commit4d agoMost recent push to the default branch.

How Workbench works

What workbench does

workbench is a self-hosted MCP tool aggregator. It brings 194 tools from 16 integrations into one endpoint, while exposing those tools through nine meta-tools rather than registering every provider tool directly with the agent. The fixed meta-tool set keeps the agent’s visible tool list consistent as integrations are connected or removed.

Supported provider examples include Jira, GitHub, Slack, and Google. The project also includes two internal integrations, browser and jots. Integrations can use OAuth 2, API keys, cookies, or no authentication, depending on the provider.

Per-user, per-provider OAuth connections are kept separately. Access tokens are encrypted at rest. Agents authenticate with a Workbench API key or OAuth 2.1, with dynamic registration and PKCE available for the latter.

How it works

An MCP client sends JSON-RPC requests to POST /mcp. The meta-tools route discovery and execution through a plugin registry, which supplies the appropriate provider credentials before calling the external API.

Non-agent callers can use POST /rest/:integration instead. This route accepts plain JSON, uses the same stored credentials, and avoids JSON-RPC framing. REST responses are not subject to the 60,000-character result cap applied to MCP results.

The portal is used to connect integrations and mint API keys. Portal single sign-on can use Google, Keycloak, or both. SQLite and PostgreSQL are supported as database backends, with a migration path between them.

Setup and configuration

A basic local setup requires cloning the repository, installing dependencies with npm install, creating .env from .env.example, and defining both required secrets:

  • ENCRYPTION_KEY, generated as a 32-byte hexadecimal value
  • SESSION_SECRET, generated as a random Base64 value

Start the development server with npm run dev. After opening the portal, connect an integration and create an API key, then configure the MCP client to use http://localhost:3000/mcp.

The project also documents Docker deployment, PostgreSQL configuration, portal SSO, security, observability, and release procedures. Development commands include npm run test, npm run build, and npm run lint.

Tools and capabilities

  • Discover and execute provider tools through nine meta-tools.
  • Maintain separate credentials for each user and provider.
  • Support OAuth 2, API-key, cookie, and unauthenticated integrations.
  • Expose the same integration actions through MCP and REST.
  • Add integrations through the plugin system, which includes a manifest reference and plugin context API.
  • Keep agent tool-list size stable across different integration combinations.

Limitations and notes

The MCP interface is intentionally indirect: agents work through nine meta-tools rather than receiving 194 individual tools. MCP results have a 60,000-character cap, although the REST route does not. The service is self-hosted, so deployment, secret management, provider setup, and portal configuration remain part of the operator’s responsibilities.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Workbench

workbench is an MCP server that connects agents to 16 integrations through one endpoint. Its nine meta-tools discover and execute 194 provider tools, including actions for services such as Jira, GitHub, Slack, and Google. It manages per-user credentials and encrypts stored tokens.

Install it by cloning the repository, running `npm install`, creating `.env` from `.env.example`, setting `ENCRYPTION_KEY` and `SESSION_SECRET`, and starting `npm run dev`. Then connect an integration in the portal, mint an API key, and use `/mcp`.

workbench keeps a separate OAuth connection for each user and provider, then encrypts tokens at rest. Supported integration authentication modes include OAuth 2, API keys, cookies, and no authentication. Agent access uses a Workbench API key or OAuth 2.1.

Yes. Scripts and cron jobs can call `POST /rest/:integration` with plain JSON instead of using JSON-RPC over `/mcp`. The REST interface uses the same stored credentials and does not apply the MCP result-size cap.

Add an integration through workbench’s plugin system. The project provides plugin documentation covering manifests, the plugin context API, and the four supported authentication modes.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWorkbench AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/workbench-2?style=directory)](https://allmcps.com/mcp/workbench-2)
HTML Embed
<a href="https://allmcps.com/mcp/workbench-2"><img src="https://allmcps.com/api/badge/workbench-2?style=directory" alt="Workbench on AllMCPs" /></a>