---
title: "MCP server: operate Tanso from an agent"
description: "Tanso ships an MCP server so agents can list plans, check entitlements, forecast usage, subscribe and buy credits over MCP instead of REST. Spend tools need explicit confirmation. Admin tools are gated separately. Off by default."
date: 2026-08-26
canonical: https://tansohq.com/product/mcp
---

# MCP server

Operate Tanso over MCP, with a consent gate on anything that spends.

The same engine, reachable from Claude, Cursor or any MCP client. A curated customer surface for your customers' agents, and an admin surface for your own, each behind its own switch.

## Two surfaces

- **Customer tools.** listPlans, getCreditPrices, checkEntitlement, getUsageForecast, subscribePlan and purchaseCredits. The last two need confirmAction before money moves.
- **Budget pre-flight.** getMyBudget lets an agent read its own key's limit, spend and remainder before it commits, so it can slow down before it gets a 403.
- **Admin tools.** Catalog, customers, credits and Stripe setup for your own operators' agents. Needs a second flag on top of MCP itself, and every tool fails closed without an admin account.

## Defaults

app.mcp.enabled is false by default. Admin tools need app.mcp.admin-tools.enabled as well. Nothing an agent can do over MCP is something it could not already do over the REST API with the same key, and the same per-key budgets apply.

## Also in Tanso

- [Agent-serve](https://tansohq.com/product/agent-serve.md)
- [Monetization](https://tansohq.com/product/monetization.md)

Code: https://github.com/tansohq/tanso-oss · Docs: https://tanso.mintlify.app