Build with TempoRevenue.

TempoRevenue MCP server

The TempoRevenue MCP server is a remote MCP server. Any MCP client that supports Streamable HTTP can connect to it and create proposal drafts from a short description of a client's request.

Listed in the official MCP Registry as com.temporevenue/proposals.

Endpoint

https://app.temporevenue.com/api/mcp

Transport

Streamable HTTP, stateless, JSON responses

Authentication

Authorization: Bearer <API key>

Tools

create_proposal, get_proposal_status, list_proposals, get_credit_balance

Tools

{
  "id": "5c0e6f3a-0b53-4a0e-9d57-6a4f6f6f2c11",
  "title": "Online store for Bloom & Co",
  "editor_url": "https://app.temporevenue.com/proposals/5c0e6f3a-0b53-4a0e-9d57-6a4f6f6f2c11"
}

{
  "status": "viewed",
  "viewed_at": "2026-10-01T14:22:09Z"
}

{
  "proposals": [
    {
      "id": "5c0e6f3a-0b53-4a0e-9d57-6a4f6f6f2c11",
      "title": "Online store for Bloom & Co",
      "status": "viewed",
      "editor_url": "https://app.temporevenue.com/proposals/5c0e6f3a-0b53-4a0e-9d57-6a4f6f6f2c11"
    }
  ]
}

{
  "credits_remaining": 12
}

Notes

• Each tool result is a JSON document in a single text content block. A failed call sets isError and returns { "error": { "code", "message" } }, using the same error codes as the REST API, except that an account with no proposals left gets no_proposals_left and a plain message, with no link.
• create_proposal can take 30 to 60 seconds, and the server allows up to 90. Set your client's tool timeout to at least 90 seconds.
• JSON-RPC batch requests are not supported and return 400.
• OAuth dynamic client registration accepts only the verified callbacks of Claude and ChatGPT and loopback addresses with a port (http://localhost:PORT, http://127.0.0.1:PORT, http://[::1]:PORT). Need another MCP client? Contact support.

Connect with an API key

1. Create a key

   Open TempoRevenue, go to Integrations, and create an API key. Copy it right away: it is shown once. Open Integrations.

2. Add the server

   Add the server to your client with the snippet for your tool (below). Replace YOUR_API_KEY with your key.

3. Ask for a proposal

   Ask: "Turn these call notes into a proposal."

Claude Code

Run this in your terminal. Claude Code guide.

claude mcp add --transport http temporevenue https://app.temporevenue.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

Claude Desktop

Needs Node.js. Add this to claude_desktop_config.json (Settings, Developer, Edit Config) and restart. Claude Code and Claude Desktop guide.

{
  "mcpServers": {
    "temporevenue": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.temporevenue.com/api/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

Cursor

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project. Cursor guide.

{
  "mcpServers": {
    "temporevenue": {
      "url": "https://app.temporevenue.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Gemini CLI

Run this in your terminal. Gemini CLI guide.

gemini mcp add --transport http temporevenue https://app.temporevenue.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

Try saying

• Turn these call notes into a proposal: [paste notes]
• Did my client open the proposal I sent last week?
• Show my last 5 proposals and which ones were accepted.
• How many proposal credits do I have left this month?

TempoRevenue API

Base URL

https://app.temporevenue.com/api/v1

Authentication

Authorization: Bearer <API key>

Format

JSON in, JSON out. Responses are sent with Cache-Control: no-store.

Spec

https://temporevenue.com/openapi.json (OpenAPI 3.1)

Listing proposals is available through the TempoRevenue MCP server (list_proposals). The TempoRevenue API has the three endpoints above.

curl -X POST https://app.temporevenue.com/api/v1/proposals \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 6f1c2a9e-bloom-store-v1" \
  -d '{"input": "Sarah at Bloom & Co needs a new online store in 3 weeks, budget $1,200.", "client_name": "Sarah", "language": "en"}'

{
  "id": "5c0e6f3a-0b53-4a0e-9d57-6a4f6f6f2c11",
  "title": "Online store for Bloom & Co",
  "editor_url": "https://app.temporevenue.com/proposals/5c0e6f3a-0b53-4a0e-9d57-6a4f6f6f2c11",
  "status": "draft",
  "public_url": "https://app.temporevenue.com/p/8Kf2vQ9mT1xLw0aZbN4cRg",
  "credits_remaining": 12
}

curl https://app.temporevenue.com/api/v1/proposals/5c0e6f3a-0b53-4a0e-9d57-6a4f6f6f2c11 \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "id": "5c0e6f3a-0b53-4a0e-9d57-6a4f6f6f2c11",
  "status": "viewed",
  "viewed_at": "2026-10-01T14:22:09Z",
  "accepted_at": null,
  "public_url": "https://app.temporevenue.com/p/8Kf2vQ9mT1xLw0aZbN4cRg"
}

curl https://app.temporevenue.com/api/v1/credits \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "credits_remaining": 12,
  "plan": "pro"
}

Statuses

There is no sent status: TempoRevenue has no send step, you share the link yourself.

Errors

Errors use the HTTP status and a JSON body with a stable code. The TempoRevenue MCP server returns the samecode values inside tool results, except that an account with no proposals left gets no_proposals_leftinstead of payment_required. Match on code, not on message.

{
  "error": {
    "code": "payment_required",
    "message": "No proposals or credits left. Buy credits or upgrade to continue.",
    "purchase_url": "https://app.temporevenue.com/usage"
  }
}

Rate limits

• TempoRevenue API: 10 requests per minute per account, on every endpoint.
• TempoRevenue MCP server: 10 create_proposal calls per minute, and 60 other calls per minute (initialize, tools/list, get_proposal_status, list_proposals, get_credit_balance).
• Limits are counted per account and per key. Creating more keys does not raise them.
• When you go over, you get 429 with a Retry-After header (seconds).

Idempotency

• Send an Idempotency-Key header on POST /proposals (1 to 255 printable ASCII characters). It is optional, and it makes retries safe.
• Repeat the same key with the same body and you get the same proposal back, with the current credits_remaining, no new generation and no new charge. The repeat carries the header Idempotent-Replay: true.
• The same key with a different body is 422 idempotency_key_reuse. The same key while the first request is still running is 409 idempotency_in_progress. Results are kept for 30 days.

curl -X POST https://app.temporevenue.com/api/v1/proposals \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 6f1c2a9e-bloom-store-v1" \
  -d '{"input": "Sarah at Bloom & Co needs a new online store in 3 weeks, budget $1,200.", "client_name": "Sarah", "language": "en"}'

Limits and pricing

• Proposals created through the TempoRevenue API or the TempoRevenue MCP server use the same credits as the app, one per proposal, and the same account quota.
• Free plan: 3 proposals per month, no credit card. Pro: $29/month, 30 proposals per month, 7-day trial.
• Pro is sold in the United States, Canada and Brazil. The free plan works anywhere.
• You can create up to 5 active API keys. One key works for the TempoRevenue API and for the TempoRevenue MCP server.

See pricing for the plans.

Security

• Keys are per user and can be revoked anytime in Integrations. A key is shown once, when you create it; we store only a hash.
• Neither the TempoRevenue API nor the TempoRevenue MCP server can send anything to your clients, and neither can edit or delete a proposal. They create drafts and read status, lists and balance.
• A proposal id that is not yours returns 404, never 403, so ids in other accounts are not revealed.
• Treat a key like a password: keep it out of source control and rotate it if it leaks.
• Content you send is processed under our privacy policy, the same as content you paste in the app.

Read the privacy policy. Questions about the TempoRevenue API:contact@temporevenue.com.