Combiner Request access
Managed MCP service

One governed endpoint for the AI tools your team uses.

Combiner is a managed MCP service that turns useful tools into approved, metered, workspace-ready capabilities. Connect a supported MCP client to one URL. Owners decide who can use what, the workspace shares one credit budget, and every call is recorded.

Endpoint https://combiner.to/mcp
Architecture
Supported clients
Claude
Supported MCP client
Combiner
OAuth sign-in Service Bundle access Credit metering Audit and denials
Services
Your team's tools
Curated and governed
The problem

Your team is already connecting AI tools. Nobody is controlling them.

Your team points AI clients at tools every day. There is no approved tool set, no shared spend limit, no per-person access, and no record of what ran or what was blocked. The tools are useful. The lack of control is the problem.

No approved set

Anyone can wire up anything. There is no agreed list of tools the team is allowed to use.

No shared budget

Paid calls run with no shared limit and no single place to watch spend.

No per-person access

Everyone gets everything, or access is managed by hand, tool by tool.

No audit

There is no record of which call ran, who made it, or why one was blocked.

What Combiner is

One managed service in front of your tools.

Your team connects an AI client to a single endpoint. Combiner authenticates the person, finds their workspace, shows only the tools they are allowed to use, meters paid calls against a shared budget, and records every call. The workspace decides access, not the URL.

MCP is the open standard that lets AI clients call external tools. Combiner is the layer that decides which tools your team can call, what they cost, and who is allowed.

Each call, in order
  1. 1
    Authenticate the person
    OAuth sign-in through WorkOS.
  2. 2
    Resolve the workspace
    Membership and role decide what is visible.
  3. 3
    Show only granted tools
    Service Bundles scope what each member can call.
  4. 4
    Meter and record
    Paid calls draw on the shared budget. Every call is audited.
Service Bundles

Access comes in bundles you grant, not a firehose you police.

Tools are grouped into Service Bundles. An owner grants a bundle to a member, and that member can use exactly the tools in it. Nothing more. Grants are additive, scoped, and reversible, and every grant and revoke is recorded. Least privilege is the default, not a setting you have to find.

Example bundle
illustrative
Read only

A bundle groups a set of tools. Grant it to a member and they can use exactly these, nothing more.

4 tools 2 free
read search fetch export
Available, members need a bundle grant
Built for teams

One governed endpoint for any team's tools.

Combiner is not a catalog you dig through. We curate and run a focused set of governed tools, and we shape access around the work a team actually does. The model is the same whatever your team works on: approved tools, a shared budget, and a record of every call. We add services deliberately, so every tool stays governed, metered, and auditable.

Shaped to the work

Access maps to what a team does, from research and operations to client work, not a generic tool dump.

Curated, not infinite

Every tool is picked, priced, run, and tested before it ships, so each one stays governed and auditable.

One model, any domain

The same approval, budget, and audit model carries across teams and the work they do.

Teams Combiner is built for
Real estate Technology Commerce Travel and tourism Research and media and more

Tell us what your team needs during early access, and we will tell you what is available today and what we can shape next.

Credits

One shared budget. Real prices. No surprise bills.

Your workspace shares one credit pool. Every paid tool has a clear credit price, and free tools stay free. The owner sees usage and denials as they happen and can cap or revoke access at any time. If a tool call fails upstream, the credits are refunded, not charged.

Owner view (illustrative example)
Credits remaining
320
Shared across the workspace
Denials today
2
Blocked calls, with a reason on each
fetch1 credit
readFree
search1 credit
Security and governance

Built so you can see and prove what happened.

Sign-in uses OAuth through WorkOS. Every call your team makes, allowed or denied, is recorded with the reason, the tool, the member, and a request id. Logging is metadata only; Combiner does not store the content of what was fetched. Workspace credentials are encrypted and never shown in plaintext after you save them.

Illustrative audit and denials view
Time Member Tool Outcome Reason
09:41 Member fetch Allowed charged 1 credit
09:43 Member search Denied no_credits
09:44 Owner read Allowed free tool
How it works

Connect once. Govern from day one.

  1. 1
    Connect your client
    Create a workspace and connect a supported MCP client to the Combiner endpoint.
  2. 2
    Grant access and set a budget
    As owner, grant a Service Bundle to each member and set the shared credit budget.
  3. 3
    Your team works
    Members use the granted tools through their own client.
  4. 4
    Watch and revoke
    Watch usage and denials, and revoke access any time, with a record of every change.
Endpoint
https://combiner.to/mcp
Client configuration
{
  "mcpServers": {
    "combiner": {
      "url": "https://combiner.to/mcp"
    }
  }
}
Why Combiner is different

Most platforms sell more tools. Combiner sells control.

Other platforms compete on how many tools they connect and how fast you can wire them in. Governance and spend control sit behind a sales contact form. Combiner inverts that. Access, budget, and audit are the product. Fewer tools, each one approved, metered, and on the record.

Curated and governed access

Service Bundles are the grant unit. Members get exactly the tools an owner approved, nothing more.

Shared spend control

One budget the owner funds and watches, with clear per-tool prices and a free versus paid split.

Owner-readable audit

Every call, allowed or denied, is on the record with the reason, the tool, and the member.

FAQ

Questions teams ask.

What is MCP, and do I need to understand it?

MCP is the open standard that lets AI clients call external tools. Combiner handles the protocol. You manage access and spend.

Which AI clients work?

Combiner is verified today with Claude Web and Claude Desktop, plus the FastMCP Inspector for testing. ChatGPT is not verified end to end yet, so it is not listed as supported.

What does it cost?

Credits are the internal unit. Paid tools have a clear credit price and free tools stay free. Pricing is handled per team during early access.

What tools can my team use?

Combiner runs a curated, governed set of tools and adds services deliberately, so every tool stays metered and auditable. Tell us what your team needs during early access, and we will tell you what is available today.

Where does my data go, and what do you log?

Logging is metadata only. Combiner does not store the content of what was fetched. Workspace credentials are encrypted and never shown in plaintext after you save them.

Is Combiner only for large teams?

No. A personal workspace is a one-person workspace. Teams add shared credits, grants, and audit on top of the same model.

Bring your team's AI tools under control.

Request access and connect your first client, or see how it works first.