Tenjin MCP Server

Why

Giving your agent good tools is a chore today:

• A key for every tool. Sign up, pick a plan, paste an API key into a config file. Five tools, five accounts.

• MCP servers crowd the context. Every server you install loads its tool definitions into every session, needed or not.

• Your agent forgets anyway. It reaches for plain web search out of habit, so you write rules to remind it, and it still slips.

• Some tools you need once. Installing something permanent for a one-off lookup isn't worth the setup.

Tenjin handles all of it. Install it once and keep working. The Tenjin router watches the moments where a tool could help: your prompt, your agent's web searches and page fetches, the tasks it hands to subagents, and the questions it asks you. When a curated tool beats what your agent was about to do, the router suggests it and your agent calls it. Your wallet pays for each call through x402, so you manage no keys and install nothing new.

Related MCP server: HiveCapital

Quick start

In Claude Code or Claude Desktop, paste:

Install Tenjin from tenjin.sh

Your agent installs it, asks you about spend limits in the session, and helps you fund the wallet.

Or in a terminal (Node.js 24 or newer):

npm i -g tenjin-cli
tenjin install          # sets up Claude Code and creates your wallet
tenjin wallet fund 2    # optional: add $2 with a card, via Coinbase

What it can do

The router picks from a catalog we curate and maintain. When nothing in it fits, it can point your agent at a reviewed third-party pay-per-call service from the Tenjin list, and your agent decides whether to use it or to ask you first. Each routing call costs a flat routing fee of $0.003, on top of the provider's price, paid from channel deposits of up to $0.25 that count against the spend limits you approve at install.

Every tool, including the Tenjin list, with current prices: tenjin.sh/tools. More are added by demand: tell us what you want.

Tenjin list and experimental Bazaar

The Tenjin list is on by default. When nothing in the catalog fits a step (such as generating a sound effect), the router may suggest one third-party pay-per-call x402 service that Tenjin has reviewed. The suggestion names the seller, the URL, the price and the input it takes, and your agent judges whether to use it or to ask you first. It is paid like any lookup, under your spend limits.

The open Bazaar is experimental and off by default. Turn it on with:

tenjin config set experimental.bazaar on

With it on, the router may also suggest sellers from Coinbase's open x402 Bazaar, and to find them, short snippets of your prompts are sent to Coinbase's public Bazaar search. Those sellers are unreviewed third parties, matches can be noisy, prices can vary with the input, and payments are real, under your spend limits. tenjin config and tenjin doctor show both settings. Turn it off with tenjin config set experimental.bazaar off.

How it works

flowchart LR
    A["Your prompt,<br>a web search,<br>or a subagent task"] --> B{"Tenjin<br>router"}
    B -- "a tool fits" --> C["Agent calls it<br>through x402"]
    C --> D["Wallet pays the provider,<br>result comes back"]
    B -- "nothing better" --> E["Agent carries on"]

The Tenjin router hooks into Claude Code at your prompt, before each web search or page fetch, when your agent hands work to a subagent, and around a question your agent asks you. At each point it asks Jev, a decision model from TypeSafe, whether a tool in the catalog fits. When none does, Jev may pick one third-party service from a short list matching the step (the Tenjin list, plus the open Bazaar if you turned it on), or none. Either way Jev only chooses from a list, so it never writes a call or an instruction for your agent; a third-party listing's description is the seller's own, and your agent judges it.

When one fits, your agent sees a one-line suggestion with the tool and its price, and calls it through Tenjin's x402 MCP server: the offer's id alone shows the tool's inputs, an example and what it returns, and the id with the agent's input runs it. Tenjin builds the call, pays the provider from your wallet, within your limits, and hands back the result. Your status line shows the call as it happens:

x402 · request: calling pro-api.coinmarketcap.com/x402/v3/cryptocurrency/quotes/latest · {"query":{"symbol":"BTC,ETH"}}

To pick a tool, the router sends your prompt and recent messages with secrets masked, plus the searches, URLs, subagent tasks and questions it routes; tool results stay on your machine. What it sends, and everything install writes →

Wallet and payments

Tenjin pays for tools with x402, an open standard that builds payments into HTTP. A paid endpoint answers 402 Payment Required with its price, the client signs a payment for that amount, and the endpoint returns the result. Neither side needs an account or an API key. Read more: x402.org · whitepaper · Coinbase docs · spec and SDKs.

Your wallet

tenjin install creates a wallet on your machine that holds USDC on Base. Tenjin encrypts the private key, unlocks it through your OS keychain, and never sends it anywhere. Tenjin never holds or moves your funds. Paying a provider costs no gas.

Limits

tenjin install asks you to approve these limits, or tells your agent to ask you when the agent runs it. How the limits work →

Routing fee

Each routing call costs a flat $0.003, paid over x402 batch-settlement by tenjin mcp from a channel deposit of up to $0.25 (less when your per-call limit is lower). A deposit is an automatic payment: it counts against the limits above, and approving them at install approves the fee. The fees come out of the deposit and are not counted again. When a call cannot be paid, it takes the free path, and Claude Code tells you once per session why and what fixes it; tenjin doctor says the same. Details are in docs/agent-permissions.md.

Funding

tenjin wallet fund 2 opens a Coinbase Onramp checkout for your wallet: pay by card, or Apple Pay where your region supports it. Sign in to Coinbase or create an account during checkout. You can also send USDC on Base to the address tenjin wallet address prints; at a terminal it and tenjin wallet fund also draw that address as a QR code for a phone wallet to scan (--no-qr skips it).

$1–2 goes a long way. $2 covers about 280 web searches, 200 page reads or 100 Wolfram Alpha answers.

Withdrawing

tenjin wallet send <amount> USDC <address> sends funds to any address. It's a regular onchain transfer, so it needs a little ETH on Base for gas.

Everyday commands

tenjin status                  # what you've spent today
tenjin wallet balance          # what's left
tenjin wallet fund 5           # top up
tenjin payments reconcile      # settle paid lookups whose settlement was unknown
tenjin update                  # newest version; wallet and settings stay
tenjin config set router.enabled false             # pause the router on this machine
tenjin config set --project router.enabled false   # ...or just in this repo
tenjin uninstall               # remove the Claude Code setup; your wallet stays

Use tenjin install --project to set it up for a single project. Add --json to any command for machine-readable output.

Every paid lookup is recorded on your machine, with the files and full results it returned. Where they live, and what payments reconcile does →

tenjin install sets Claude Code's status line only if you don't already have one. If you do, yours is left alone and the install prints a command that shows both; tenjin install --status-line compose writes it for you, and --status-line skip leaves the setting untouched. The status line reads local files only: no network, no wallet, and it can't affect a lookup or a payment.

Limits are set only where no setting exists yet, so an update never overwrites yours. The daily budget is a rolling 24-hour window. Setting either limit to 0 blocks automatic payments; tenjin config set sessionBudget none removes the daily ceiling only.

tenjin pay <url> pays any x402 endpoint you name. It ignores the automatic limits and always asks for your consent to the quoted price, interactively or with --yes. It is never used as a workaround when the router refuses. See the safety model.

Request a tool

Tenjin is in alpha, and the catalog grows with what people ask for. Missing a service your agent keeps needing? Hit a lookup that went to the wrong place? We want to hear it.

• Request a tool →

• Report a bug →

Learn more

• How a lookup runs, what it sends, and what install writes

• Safety model

• Troubleshooting, including a stray x402 server in ~/.mcp.json after 0.1.0-alpha.18

Developing

Before contributing, read CONTRIBUTING.md for the contributor agreement.

pnpm install
pnpm run githooks   # once, to use the repo's git hooks
pnpm run build
pnpm run test
pnpm run typecheck
pnpm run lint