Mu
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Code-map tools for AI agents: see a repo's structure first, then edit only what matters.
This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order
| 1. In Claude’s connector directory | No | |
|---|---|---|
| 2. Tried by our team | No | |
| 3. Works for Thai users | No | |
| 4. Usage without stars | 20/100 | Popularity 0 · Freshness 12 · Still answering 8 · Likes from users +0 |
| 5. Listed on | 2026-10-09 |
Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.
Quality: Passed 4/5 basic checks (shown, not used for ordering)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Itamos MCP Tools. Follow https://mcp.popnx.com/i/itamos-technologia-itamos-mcp-tools.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 4/5 checks · What you ask goes through the maker’s server (mcp.itamos-technologia.com) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Itamos MCP Toolshttps://mcp.itamos-technologia.com/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsItamos MCP Tools
Use Itamos MCP Tools and tell me what you can do for me, then show me one thing✓ If Claude says it is using Itamos MCP Tools or shows a Itamos MCP Tools tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Itamos MCP Toolshttps://mcp.itamos-technologia.com/mcpStart a new chat and pick Itamos MCP Tools from your plugins before typing
Use Itamos MCP Tools and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Itamos MCP Tools or shows a Itamos MCP Tools tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user itamos-tools https://mcp.itamos-technologia.com/mcpYou should see Itamos MCP Tools listed as connected
Use Itamos MCP Tools and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Itamos MCP Tools or shows a Itamos MCP Tools tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Itamos MCP Tools and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Itamos MCP Tools or shows a Itamos MCP Tools tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Itamos MCP Tools and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Itamos MCP Tools or shows a Itamos MCP Tools tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://mcp.itamos-technologia.com/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user itamos-tools https://mcp.itamos-technologia.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"itamos-tools": {
"url": "https://mcp.itamos-technologia.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"itamos-tools": {
"type": "http",
"url": "https://mcp.itamos-technologia.com/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026
The registry name was verified with the GitHub account itamos-technologia, which owns the repo
Code last changed 21 days ago
GitHub could not identify the licence type; open the file to check
Responded in 319 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/itamos-technologia-itamos-mcp-tools)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 4 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 21 days ago, and the latest version (1.1.0) reached the registry 39 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: Mu, Award Travel Finder, Killbottleneck, Whimsical, HasData Google Maps
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Search award flight availability and points pricing across 27 airlines and 23 loyalty programs.
Free-to-self-host goal and process maps for humans and AI agents, with REST API and MCP.
Create and edit flowcharts, mind maps, wireframes, and docs in Whimsical, or search your workspace.
Google Maps places, reviews, contributor history, photos and posts as JSON. No Google Cloud.
| This one Itamos MCP Tools | Mu | Award Travel Finder | Killbottleneck | Whimsical | HasData Google Maps | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | Yes | No | Yes |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 4/5 | 4/4 | 3/3 | 3/3 | 4/4 | 5/5 |
| License | NOASSERTION | AGPL-3.0 | MIT | MIT | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Built in Greece, for the world.
Free and open source under AGPL-3.0. Commercial licences for closed-source use.
Every LLM coding assistant faces the same wall: codebases are too large to fit in context. The standard response is to dump files — grep for something promising, cat it, hope for the best. At 50k files this breaks. At 240k files it never worked.
We built four tools that give an LLM structured perception of a codebase instead of raw file access, plus a sandboxed git to bring code in. The result is a model that navigates code the way a senior engineer does — starting from the architecture, narrowing to the module, reading only the segment it needs. One call takes it from the project straight to the lines it needs, and every save is checked before it lands.
Read the full paper: docs/PAPER.md: how each tool works, why it was designed that way, and how the hosted sandbox runs, with diagrams.
| Tool | What it does |
|---|---|
| read_file | The single entry point. With no path it lists your projects; a project name shows its structure with coordinates (no code); a coordinate opens a file map or one segment in a single call. Edits one segment at a time, and every save is verified automatically. |
| master_architect | The engine behind read_file. Indexes the codebase into a graph (files, imports, databases, servers) and keeps it in step with every save. In the sandbox it is not called directly: read_file does it. |
| write_file | Creates new files only and never overwrites; edits go through read_file. Every new file belongs to a project the agent names: an existing one, or a new name to start one. Nothing is placed automatically. |
| git | The original Itamos git tool, sandboxed for security: clone (remote URLs only, depth=1), status, commit. A clone is scanned into a project as soon as it finishes. Everything stays inside the session workspace; push is not available. |
| web_skeleton | LLM-first web perception. 97% token reduction vs raw HTML. Actions: search, skeleton, read, click. |
At least 97% fewer tokens than the usual shell workflow (grep, cat, run_cmd), measured against the best case where the model fixes the bug in one attempt. Real sessions save more, because the failed attempts common with raw shell access aren't counted.
Every client gets an isolated workspace. No shared state, no cross-session leakage. Workspaces are wiped after 10 minutes of inactivity.
read_file() → your projects
read_file(path="itsdangerous") → the structure: folders and files with coordinates, no code read_file(path="itsdangerous", segment="d.a.f") → the map of signer.py, one line per segment read_file(path="itsdangerous", segment="d.a.f.31.17") → the code of verify_signature, nothing else
Coordinates: letters are location (folders and files share one sequence per folder), numbers are what is inside a file. d.a.f.31.17 reads as src → itsdangerous → signer.py → segment 31.17. A folder that has never been scanned is scanned on first read; a cloned repository is scanned as soon as the clone finishes.
Nothing is dumped: a structure or file map over ~3,000 tokens returns an overview and asks for a search term instead. search works on both: file and folder names in a project, segment names in a file. trace=true shows what a file connects to, or a project's data flow.
Files are parsed into named segments. A 5000-line file might have 40 segments; its map is one line per segment, with classes listing their methods. The model reads the map, picks the segment it needs, reads that segment. Total context used is roughly 120 lines instead of 5000.
One edit at a time, and only on segments the model has read since the last change, so it can never change code it has not looked at. Saving verifies the file first:
| Level | Checks | On failure |
|---|---|---|
| L1 | Syntax: tree-sitter plus the language's own checker (py_compile, node --check, php -l, bash -n, gofmt, C/C++ in project context, config parsers) | Not saved; the error names the line |
| L2 | Config files through their service's checker (nginx -t, sshd -t, visudo, systemd-analyze). Linters run too | Config failure: not saved. Linter findings are only reported |
| L3 | Connections: every local import resolves to a project file (Python and JavaScript/TypeScript: any other import must be an installed package, for Python in the project's venv when it has one); SQL is checked against the live database schema | Saved, with what is incomplete and how to see it, so a project's first files can import files that don't exist yet |
L3 checks the content being saved, not an older index, and every save re-indexes the file in every supported language, so the map never lags behind the disk.
Raw HTML of a modern web page runs 50,000 to 200,000 tokens. web_skeleton output is 500 to 3,000 tokens. The model reads the skeleton, picks the section id it needs, reads that section only.
Verified in live use with Claude Opus 5.5 and Claude Sonnet. Any MCP-capable model can use the tools.
Don't take our word for it. Test the tools free in the hosted sandbox with your own model and your own repository, then post your results in Discussions → Benchmarks: model, task, tokens, time.
Found a bug? Open an issue with the steps to reproduce it. Every report makes the tools better.
The sandbox server speaks standard MCP over HTTP POST with SSE support.
Compatible with any MCP client. Used in practice through Claude.ai and through direct API integration (our benchmark harness).
Try it in Claude (free live alpha): copy https://mcp.itamos-technologia.com/mcp, open Claude's connector settings, click Add custom connector, paste the address and click Add. A page opens with one button, Create my sandbox: no account, no email. Switch it on in a chat (+ → Connectors) and ask, for example, *"Go to bbc.com/news and tell me the top stories."* In other MCP clients, add the same address as a remote MCP server. Sandboxes are deleted after 10 minutes of inactivity, so don't use them for sensitive data.
apt install build-essential python3).git clone https://github.com/itamos-technologia/itamos-mcp-tools.git
cd itamos-mcp-tools npm install
One npm install sets up everything, including the tools folder.
On Ubuntu 26.04 you can install the package from Releases instead: sudo apt install ./itamos-mcp-tools_1.1.0_all.deb. It sets up a service user, a systemd service, settings in /etc/itamos-mcp-tools/env and the command itamos-mcp-create-slots, then tells you the next two steps.
Besides the standard tree-sitter grammars (installed by npm install), read_file and the segmenter use extra parsers from the grammars/ folder:
| Files | Parser | Falls back to |
|---|---|---|
.cu .cuh .hip | tree-sitter-cuda-plus | stock tree-sitter-cuda, then C++ |
.metal | tree-sitter-metal-plus | tree-sitter-metal, then C++ |
.cpp .cc .hpp, C++ .h | tree-sitter-cpp-plus | stock tree-sitter-cpp |
.m .mm, .h with @interface | tree-sitter-objc | C / C++ |
The "plus" parsers are the stock grammar plus extra C++ rules, checked to give the identical tree wherever the stock grammar already parses. A parser that is missing or fails to load is skipped, never fatal.
grammars/tree-sitter-*/prebuilds/linux-x64/ (Node-API, any Node 18+, glibc 2.14+), and npm install sets up the rest. cd grammars/tree-sitter-cuda-plus && npx node-gyp rebuild # same for tree-sitter-cpp-plus, -metal-plus, -metal
grammars/tree-sitter-* folder is a self-contained package. Copy one in and the sandbox finds it by name, with no install or symlink. To keep the grammars somewhere else, set SANDBOX_GRAMMARS_DIR.grammars/plus/): grammars/plus/build_plus.sh generates with tree-sitter-cli 0.25.10 (ABI 15), compiles, and publishes into the matching tree-sitter-* folder. Its header shows the arguments.sudo scripts/create-slots.sh tank/sandboxes 500 2G $USER
This creates slot_001 to slot_500 under the ZFS dataset tank/sandboxes (use your own pool name), each with a 2 GB quota and lz4 compression, owned by the user the server runs as. It is safe to run again.
SANDBOX_ROOT=/tank/sandboxes SANDBOX_TOTAL_SLOTS=500 npm start
From the same machine, add http://localhost:4200/mcp as a connector in your MCP client. Local connections are identified by IP address and need no sign-in.
Firewall port 4200 and put an HTTPS reverse proxy (for example nginx) in front of it that sets X-Forwarded-For and X-Forwarded-Proto. Requests that arrive through the proxy use the anonymous one-click sign-in, so users on shared addresses (such as claude.ai) each get their own sandbox. Direct connections to port 4200 skip the sign-in, which is why the port must not be reachable from outside.
read_file and web_skeleton give untitled paragraphs and page sections a short title (5 to 10 words) from a small summarizer model, so the agent can tell parts apart without reading them. Without a summarizer everything still works; those parts are then named by their first line.
Any OpenAI-compatible chat endpoint works, set with ITAMOS_SUMMARIZER_URL (default http://127.0.0.1:8090): a single llama-server, Ollama, or the included router in front of several GPUs. The whole paragraph is always sent, never cut.
The hosted sandbox runs Gemma 4 E4B (Q4_0) as summarizer and EmbeddingGemma 300M as embedder on three GPUs (one 16 GB MI50 and two 8 GB V340 dies), each summarizer started like this:
llama-server -m gemma-4-E4B-it-Q4_0.gguf -ngl 99 --port 8190 \
-np 64 -c 524288 --kv-unified -fa on --cache-type-k q4_0 --cache-type-v q4_0 -rea off
--kv-unified: one shared KV pool, so each request uses only the tokens it needs.--cache-type-k q4_0 --cache-type-v q4_0 (needs -fa on): a 4-bit KV cache, about 4.5 KB per token for this model.-c is the pool in tokens: 524,288 on the MI50, 262,144 on each V340 die (with 32 slots).The router (router/llm-router.js, service itamos-llm-router) listens on 8090 (summarizer) and 8091 (embedder). Before sending a request it counts its tokens with the backend's own tokenizer, sends it to a GPU whose pool has room (preferring faster GPUs by weight), and makes it wait in line when none has. A GPU that fails is skipped for 15 seconds and the request is retried on another. Configure it with ROUTES (in the package: /etc/itamos-mcp-tools/router.env); GET /router/status shows each GPU's pool, reserved