Preparing page

Loading product graph, proof, and adoption context.

Preparing tokens&

Loading the next builder or enterprise surface.

Request pilot pricing

Agent-native distributionCodex plugin readyMCP ready

Install where builders already work

Put Tokens& inside Codex, Cursor, Claude Code, and VS Code.

Builders should not browse a directory when they are shipping. The Tokens& Agent Pack gives coding agents stack choices, perks, Build Packets, launch proof steps, and approval boundaries from the workflow they already use.

Generate build packet Create scoped token

agent-pack

Public manifest: /.well-known/tokensand-agent-pack.json

OpenAPI

https://tokensand.com/openapi.json

MCP config

https://tokensand.com/api/workflow/mcp-config

Codex plugin

plugins/tokensand-agent-pack

Cursor plugin

plugins/tokensand-cursor-plugin

Codex

plugin-ready

Bring Build Packets, saved stack context, enterprise session analysis, perks, and proof workflow guidance into Codex.

Install the Tokens& Codex plugin for public stack search and enterprise session briefs, then add scoped credentials when private project or workspace context is needed.

Get config

Cursor

mcp-ready

Let Cursor ask for Tokens& builder or enterprise context before implementation, session follow-up, and proof publishing.

Open the installer for public stack search and enterprise session briefs. Add a scoped workflow token later for private Build Packets and project proof.

Open installer

Claude Code

mcp-ready

Give Claude Code the selected stack, cost, safety, docs, and proof plan without copying website text.

Use the same Tokens& MCP server command. Add DAI_TOKEN only when private project context is required.

Get config

npm

publish-ready

Give every agent host one stable package specifier and avoid cache misses from versioned tarball URLs.

Publish the CLI package publicly, then use the npm package name instead of the hosted tarball in every MCP config.

Get config

VS Code

mcp-ready

Keep stack decisions and project proof visible beside the repo.

Use the Codex IDE extension or a compatible MCP client. Public search works first; scoped tokens unlock project context.

Get config

Install path

1Install the public MCP config for stack search and agent guidance.
2Ask the agent to call search_tools when choosing a stack.
3Sign in only when a builder wants private saved stack, Build Packet, or project context.
4Generate a scoped DAI_TOKEN from the project workflow and add it to the MCP config.
5Tell the coding agent to call get_build_packet before implementation once the token is attached.

Paste-ready config

Open Cursor installer

Codex TOML

[mcp_servers.tokensand]
command = "npx"
args = ["-y", "@dev-adoption/cli@0.1.9", "mcp", "serve", "--api", "https://tokensand.com"]

Cursor / MCP JSON

{
  "mcpServers": {
    "tokensand": {
      "command": "npx",
      "args": [
        "-y",
        "@dev-adoption/cli@0.1.9",
        "mcp",
        "serve",
        "--api",
        "https://tokensand.com"
      ]
    }
  }
}

Claude Code

claude mcp add --transport stdio tokensand -- npx -y @dev-adoption/cli@0.1.9 mcp serve --api https://tokensand.com

npm after publish

npx -y @dev-adoption/cli@0.1.9 mcp serve --api https://tokensand.com

Agent workflow contract

Choose the stack

Ask Tokens& build_brief before code changes when the user is choosing tools, backend, auth, data, deployment, cost, credits, APIs, or proof path. For customer-agent builds, require best APIs, cost drivers, free credits/perks, and dashboard sync status.

/api/workflow/build-packet/api/build/search/api/perks

Find useful builder offers

Check public perks and credits that match the selected stack. Do not imply a perk is guaranteed until the user claims it.

/api/perks

Publish proof only after review

Draft repo, demo, stack, launch source, and notes first. Public proof publishing requires explicit human approval.

/api/workflow/context/api/workflow/build-packet/api/workflow/projects

Return enterprise session signal

Use get_account_mode first, then call enterprise_session_brief for source-labeled funnel rates, costs, ICP segment guidance, session format, dashboard handoff, and proof boundaries. Self-reported proof is not verified until first-party, public-source, consented, or aggregate-safe evidence clears the gate.

/api/v1/adoption/api/v1/agent-rank/api/usage/track/dry-runmcp:enterprise_session_brief

Draft adoption motion

Draft the adoption session, ICP invite batch, Invite partner company motion, or proof plan inside the agent. For sessions, accept sourceProvider luma/partiful/eventbrite/zoom/manual plus a public sourceUrl, never API keys. Require dashboard approval before any Tokens& write or external send.

mcp:draft_adoption_sessionmcp:draft_icp_invite_batchmcp:draft_partner_invitemcp:draft_adoption_proof_motion

Safe by default

Private saved stacks, project context, live enterprise tenant metrics, and write actions require a signed-in session or scoped workflow token.

Tokens& creates tracking, partner intake, ICP preview, and proof. It does not create Luma/Zoom/Eventbrite pages or send external invites without approval.

Public adoption reads are aggregate and source-labeled; raw developer identity and tenant-scoped enterprise metrics stay private.

Supply-side growth loop

Enterprise teams add offers. Builders claim them inside the agent workflow. Projects publish proof. Vendors get source-labeled adoption signals and improve the next offer.

Add builder offer

Preparing page

Loading product graph, proof, and adoption context.

Agent-native distributionCodex plugin readyMCP ready

Install where builders already work

Put Tokens& inside Codex, Cursor, Claude Code, and VS Code.

Generate build packet Create scoped token

agent-pack

Public manifest: /.well-known/tokensand-agent-pack.json

OpenAPI

https://tokensand.com/openapi.json

MCP config

https://tokensand.com/api/workflow/mcp-config

Codex plugin

plugins/tokensand-agent-pack

Cursor plugin

plugins/tokensand-cursor-plugin

Codex

plugin-ready

Bring Build Packets, saved stack context, enterprise session analysis, perks, and proof workflow guidance into Codex.

Install the Tokens& Codex plugin for public stack search and enterprise session briefs, then add scoped credentials when private project or workspace context is needed.

Get config

Cursor

mcp-ready

Let Cursor ask for Tokens& builder or enterprise context before implementation, session follow-up, and proof publishing.

Open the installer for public stack search and enterprise session briefs. Add a scoped workflow token later for private Build Packets and project proof.

Open installer

Claude Code

mcp-ready

Give Claude Code the selected stack, cost, safety, docs, and proof plan without copying website text.

Use the same Tokens& MCP server command. Add DAI_TOKEN only when private project context is required.

Get config

npm

publish-ready

Give every agent host one stable package specifier and avoid cache misses from versioned tarball URLs.

Publish the CLI package publicly, then use the npm package name instead of the hosted tarball in every MCP config.

Get config

VS Code

mcp-ready

Keep stack decisions and project proof visible beside the repo.

Use the Codex IDE extension or a compatible MCP client. Public search works first; scoped tokens unlock project context.

Get config

Install path

1Install the public MCP config for stack search and agent guidance.
2Ask the agent to call search_tools when choosing a stack.
3Sign in only when a builder wants private saved stack, Build Packet, or project context.
4Generate a scoped DAI_TOKEN from the project workflow and add it to the MCP config.
5Tell the coding agent to call get_build_packet before implementation once the token is attached.

Paste-ready config

Open Cursor installer

Codex TOML

[mcp_servers.tokensand]
command = "npx"
args = ["-y", "@dev-adoption/cli@0.1.9", "mcp", "serve", "--api", "https://tokensand.com"]

Cursor / MCP JSON

{
  "mcpServers": {
    "tokensand": {
      "command": "npx",
      "args": [
        "-y",
        "@dev-adoption/cli@0.1.9",
        "mcp",
        "serve",
        "--api",
        "https://tokensand.com"
      ]
    }
  }
}

Claude Code

claude mcp add --transport stdio tokensand -- npx -y @dev-adoption/cli@0.1.9 mcp serve --api https://tokensand.com

npm after publish

npx -y @dev-adoption/cli@0.1.9 mcp serve --api https://tokensand.com

Agent workflow contract

Choose the stack

/api/workflow/build-packet/api/build/search/api/perks

Find useful builder offers

Check public perks and credits that match the selected stack. Do not imply a perk is guaranteed until the user claims it.

/api/perks

Publish proof only after review

Draft repo, demo, stack, launch source, and notes first. Public proof publishing requires explicit human approval.

/api/workflow/context/api/workflow/build-packet/api/workflow/projects

Return enterprise session signal

/api/v1/adoption/api/v1/agent-rank/api/usage/track/dry-runmcp:enterprise_session_brief

Draft adoption motion

mcp:draft_adoption_sessionmcp:draft_icp_invite_batchmcp:draft_partner_invitemcp:draft_adoption_proof_motion

Safe by default

Private saved stacks, project context, live enterprise tenant metrics, and write actions require a signed-in session or scoped workflow token.

Tokens& creates tracking, partner intake, ICP preview, and proof. It does not create Luma/Zoom/Eventbrite pages or send external invites without approval.

Public adoption reads are aggregate and source-labeled; raw developer identity and tenant-scoped enterprise metrics stay private.

Supply-side growth loop

Enterprise teams add offers. Builders claim them inside the agent workflow. Projects publish proof. Vendors get source-labeled adoption signals and improve the next offer.

Add builder offer