Tokencost Dev vs Prompts.chat MCP

A side-by-side look at the Tokencost Dev and Prompts.chat MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Tokencost Dev logoTokencost DevConversational AI · Local subprocess (stdio)LLM pricing oracle — model lookup, cost estimation, and comparison via LiteLLM60GoodAuth: not declaredPrompts.chat MCP logoPrompts.chat MCPConversational AI · Local subprocess (stdio)A MCP server for prompts.chat55GoodAuth: not declared

Verdict: choose Tokencost Dev for conversational ai work as a local process; choose Prompts.chat MCP for conversational ai as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Tokencost Dev logoChoose Tokencost Dev when

  • You need dedicated capabilities in the Conversational AI domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like get_model_details, calculate_estimate, compare_models.
Explore Tokencost Dev

Prompts.chat MCP logoChoose Prompts.chat MCP when

  • You need dedicated capabilities in the Conversational AI domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PROMPTS_API_KEY, PROMPTS_QUERY.
  • You want tools like search_prompts, get_prompt.
Explore Prompts.chat MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTokencost Dev logoTokencost DevPrompts.chat MCP logoPrompts.chat MCP
CategoryConversational AIConversational AI
Quality signal60/100 · Good55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedPROMPTS_API_KEYPROMPTS_QUERY
Verified ownerCommunity listingCommunity listing
GitHub stars136
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools42

Tools & capabilities

Tokencost Dev tools 4

  • get_model_detailsLook up pricing, context window, and capabilities for an LLM model. Uses fuzzy matching so you don't need the exact model key.
  • calculate_estimateEstimate the cost for a given number of input and output tokens on a specific model. Supports optional cached_tokens for prompt caching discounts.
  • compare_modelsFilter and compare models by provider, minimum context window, or mode. Returns top 5 most cost-effective matches.
  • refresh_pricesForce a re-fetch of pricing data from the LiteLLM registry. Use this if you suspect the cached data is stale.

Prompts.chat MCP tools 2

  • search_promptsSearch for AI prompts by keyword. Returns matching prompts with title, description, content, author, category, and tags.
  • get_promptGet a prompt by ID. If the prompt contains template variables (like ${variable} or ${variable:default}), you may need to provide values for them.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Tokencost Dev

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tokencost-dev": {
      "command": "npx",
      "args": [
        "-y",
        "tokencost-dev"
      ]
    }
  }
}

Prompts.chat MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "prompts-chat-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fkadev/prompts.chat-mcp"
      ],
      "env": {
        "PROMPTS_API_KEY": "YOUR_PROMPTS_API_KEY_HERE",
        "PROMPTS_QUERY": "YOUR_PROMPTS_QUERY_HERE"
      }
    }
  }
}

Frequently asked questions

Tokencost Dev is categorized under Conversational AI and uses a local stdio subprocess. Prompts.chat MCP belongs to Conversational AI and uses a local stdio subprocess. Pick Tokencost Dev for conversational ai work and Prompts.chat MCP for conversational ai.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Tokencost Dev has no declared pricing — check the project's own site. Prompts.chat MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add tokencost-dev and prompts-chat-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Tokencost Dev has a quality signal of 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Prompts.chat MCP has 55/100 (Good) with 3 views, 0 installs and 36 GitHub stars.