{"slug": "tokencap-v1-5-making-mcp-feel-invisible", "title": "TokenCap v1.5 — Making MCP Feel Invisible", "summary": "TokenCap v1.5 introduces automatic MCP configuration for AI coding tools, eliminating manual setup. The update detects tools like Claude Code, Cursor, VS Code, Windsurf, and Codex, and writes the appropriate Local MCP configuration with a single command. TokenCap remains local-first, keeping repository intelligence on the user's computer.", "body_md": "Two days ago, I released **TokenCap v1.4.0** with support for **Local MCP (Model Context Protocol)**.\n\nThe response was great, but while using it myself, I realized something.\n\nThe difficult part wasn't MCP.\n\nIt was **everything around it**.\n\nEvery AI coding tool has its own configuration format and setup process. Whether you're using Claude Code, Cursor, VS Code, Windsurf, or Codex, the first few minutes usually look the same:\n\nIt isn't complicated, but it's unnecessary friction.\n\nInstead of asking developers to configure MCP manually, why not let TokenCap do it?\n\nThat's exactly what **TokenCap v1.5** introduces.\n\n```\ntokencap mcp --init\n```\n\nOne command.\n\nTokenCap detects the AI coding tool you're using and writes the appropriate Local MCP configuration automatically.\n\nWhether you're working in:\n\n…the setup process becomes the same.\n\nRun one command and start coding.\n\nOne principle guided this release:\n\nDevelopers shouldn't have to visit multiple documentation pages just to connect their AI to their repository.\n\nThe best setup process is the one you barely notice.\n\nWhile automatic MCP configuration is the headline feature, v1.5 also includes several improvements behind the scenes:\n\nThese aren't flashy features, but they make the everyday experience noticeably better.\n\nOne thing hasn't changed since the first release.\n\nTokenCap remains **local-first**.\n\nYour repository intelligence stays exactly where it belongs—on your computer.\n\nEvery release of TokenCap has been moving toward the same goal:\n\nMaking AI coding assistants understand repositories without developers constantly thinking about context.\n\nv1.5 is another step in that direction.\n\nNot by adding more features.\n\nBut by removing one more thing developers shouldn't have to do.\n\n**Website:** [https://tokencap.vansharora.app](https://tokencap.vansharora.app)\n\n**npm:** [https://www.npmjs.com/package/tokencap](https://www.npmjs.com/package/tokencap)\n\nI'd love to hear your thoughts or feedback if you give TokenCap a try.", "url": "https://wpnews.pro/news/tokencap-v1-5-making-mcp-feel-invisible", "canonical_source": "https://dev.to/vansharora21/tokencap-v15-making-mcp-feel-invisible-4ha4", "published_at": "2026-07-18 20:17:23+00:00", "updated_at": "2026-07-18 20:27:52.683885+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "large-language-models"], "entities": ["TokenCap", "MCP", "Claude Code", "Cursor", "VS Code", "Windsurf", "Codex"], "alternates": {"html": "https://wpnews.pro/news/tokencap-v1-5-making-mcp-feel-invisible", "markdown": "https://wpnews.pro/news/tokencap-v1-5-making-mcp-feel-invisible.md", "text": "https://wpnews.pro/news/tokencap-v1-5-making-mcp-feel-invisible.txt", "jsonld": "https://wpnews.pro/news/tokencap-v1-5-making-mcp-feel-invisible.jsonld"}}