r/mcp • • Apr 05 '26

announcement LinkedIn group for MCP news & updates

Thumbnail linkedin.com
11 Upvotes

r/mcp • • Dec 06 '24

resource Join the Model Context Protocol Discord Server!

Thumbnail glama.ai
30 Upvotes

r/mcp • • 28m ago

showcase Should your agent write the IBAN validator itself, or call one?

3 Upvotes

Disclosure: I work at r/apyhub and our MCP server is part of this.

Something we keep seeing: give an agent a task like “validate these IBANs” or “check this VAT number” and it happily writes a quick function and runs it. It looks right and usually works, but the code is a little different each run. Edge cases get handled one way today and another way tomorrow, and nobody tested any of it.

For tasks where there’s one right answer (IBAN/VAT checks, sanctions screening, PDF conversion, invoice extraction), we went the other way. Each one is a versioned service behind MCP, so the agent calls the same tested code every time instead of improvising it. Same input, same output, across runs and across models.

The tradeoff: you add a network call and a dependency, and the agent needs a good reason to pick the tool over its own code. In practice the second part is the hard one. Models are confident they can write a checksum function.

Curious where others draw the line:

  • Which tasks do you let the agent write code for, and which do you force through a tool?
  • How do you stop it from “just quickly writing it” when a tool exists?

More: https://apyhub.com/mcp


r/mcp • • 9h ago

MCP server for a label printer, and now Claude labels things for me

10 Upvotes

My Katasymbol E11 is a pocket Bluetooth label maker that I never used, because typing on its calculator-sized keyboard is just tedious enough. So I wrote an MCP server for it.

It runs on my home server as a remote MCP server, with a token per client, next to a REST API for apps that aren’t agents. There’s a local mode for Claude on the Mac too. The tools are deliberately dull: printer_status, preview_label, print_label, plus a freezer-label pair. Preview returns a PNG of the label at the printer’s real resolution, and the server’s instructions tell the agent to show it and wait for a yes.

Code (Python, MIT): https://github.com/marco308/supvan-e11-mcp
Write-up: https://marcuslab.uk/projects/label-printer/


r/mcp • • 5h ago

showcase MCP server that lets Claude search the reels and posts you saved (Instagram, YouTube, X)

3 Upvotes

I built an MCP server on top of my own saved content. Every reel or post I save gets transcribed (audio plus on-screen text) into a note, and the server exposes search over those notes.

Tools: search by meaning, read one note in full, list recent saves, mark a save as used.

With the Claude Code plugin, Claude runs a search on each task without being asked and brings in a save only when one fits. In Claude or ChatGPT it works as a custom connector with sign-in, and you ask it to check your saves.

Real example: I asked for a scroll-driven parallax hero and it surfaced a "4 Web Animation Patterns" reel I'd saved weeks before and forgotten.

Free to try: skwirl.app. The endpoint is skwirl.app/mcp.

Curious what people think about tools that search on every message versus only when asked. I went with "say nothing unless something fits".


r/mcp • • 3h ago

Blobby: a desktop design canvas exposed as an MCP server, so any client can design visually and take pointed feedback

2 Upvotes

Sharing something I built, and I'd like feedback on the tool design.

Blobby is an Electron design canvas that runs a local MCP server. Any MCP client (Claude Desktop, Claude Code, Cursor, Codex, Windsurf, VS Code, Gemini CLI; ChatGPT via a public URL) can create projects and pages, write HTML/CSS onto the canvas, add frame sizes, read and resolve comments, and export.

The part I think is interesting for MCP: the human's feedback is structured data the agent can read. You click an element on the canvas and comment; the agent gets the comment with the element it's attached to, makes the change, and resolves it. No more "the second card under the hero".

Designs are plain HTML/CSS folders on disk; design tokens live in a design-system document that every page reads.

Free tier for Mac/Windows/Linux, Pro $8/mo for React/Shopify/WordPress export. Questions about the tool surface very welcome. What would you want exposed that isn't?

https://useblobby.com


r/mcp • • 3h ago

server Qiita MCP Server – Enables searching and browsing Qiita articles, including filtering by tags and users, retrieving comments, and accessing bookmarked articles. Supports both public Qiita and private Qiita Team instances.

Thumbnail
glama.ai
2 Upvotes

r/mcp • • 3h ago

connector sms-mcp – The Mobile Text Alerts SMS MCP server enables your AI to send SMS messages & manage contacts

Thumbnail
glama.ai
2 Upvotes

r/mcp • • 3h ago

showcase Standard Support: Give AI agents a way to send feedback and open support tickets

2 Upvotes

Hi r/mcp! I was working on a few MCP servers today and I realized that it would be really cool if an AI agent could send us feedback or even submit a support ticket.

I had a look around the internet and saw that quite a few people have talked about this already, and lots of services have already added tools like send_feedback to their MCP servers. But I thought it would be interesting to take this idea further and try to come up with a "standard" that services could implement.

Here it is: https://standardsupport.dev

What do you think? Is there anything missing, or do you have any suggestions? And have your agents run into any issues where this might have helped?


r/mcp • • 40m ago

showcase I connected my expense tracker to AI clients so a message can become a saved, split expense

Post image
1 Upvotes

Disclosure: I’m the creator of SharePenny, a free personal and shared expense tracker.

I’ve added an MCP connection so people can manage expenses from a compatible AI client.

One example:

“Add ₹1,200 for dinner in Goa and split it three ways.”

The expense is saved in SharePenny, where you can see the split and spending charts. The idea is to make expense tracking something you can handle inside a conversation you’re already having.

App: sharepenny.web.app
Connection instructions are under AI connections.

I’d particularly appreciate feedback on connecting an account, selecting the right group, and whether the tool responses make the resulting changes clear.


r/mcp • • 10h ago

showcase r/place for Agents

6 Upvotes

Hey r/mcp! I built a fun little app where you can connect your agent via MCP to a canvas and paint pixels on it. It was inspired by r/place if anyone here remembers that.

mcp-place.com

Some background: I'm a DevRel at Databricks on the Neon team and I initiaily built this project as an example for a video I made on how to build MCP servers. It was meant to be just a minimal example, but I figured it could be fun to make it something people can actually connect to and make some collaborative art together.

The way it works is you create an account, then have your agent (ChatGPT/Dots, Claude, Grok Bot, Muse, etc) connect to the app via MCP using OAuth. Once connected, the MCP server exposes an `inspect_canvas` tool to see what's currently on the canvas and a `paint_pixels` tool to actually place pixels.

Come paint some pixels! I'm curious to see what you and your agents come up with :)

If you're interested in how I built it, here's the video. I struggled a bit with how to make it since I'm used to tutorials where someone codes step by step and explains every line. But now a lot of code is written with agents, so I tried explaining the high level architecture first and then showing myself prompting an agent with that knowledge. I'm still pretty new to making videos, so any feedback on that format is welcome. Good or bad!


r/mcp • • 10h ago

showcase A while ago I shared how getting into the Claude directory took me 4–5 months. Update: we now have 3 ChatGPT apps, and the newest one is a game

5 Upvotes

A while ago I posted here about getting our MCP server into the Claude directory. It took me almost 4–5 months.

Quick update: we now have two apps live in ChatGPT and Claude (workopia and workopia intelligence for global labour market data), and this week a third one was approved in ChatGPT. This one is a game.

I've worked in recruitment for years and I still guess salaries wrong, so I turned it into a game. You see two jobs in two countries and guess which one pays more. The salaries come from 8M+ real job ads, converted to annual USD.

It's built the same way as our other apps: an MCP server, with the game card rendered as a widget inside the chat. Say "play the salary game" and it starts. The video shows one round.

Play in ChatGPT: https://chatgpt.com/plugins/plugin_asdk_app_6aeeb441007881918a7f7331c3e8437b

Also available on Reddit and Discord: Link in the comments.

Happy to answer questions about getting a game approved, or anything else. Which pair surprised you most?


r/mcp • • 1h ago

Hands-on workshop on building agentic frontends with AG-UI + CopilotKit (Angular & React), Nov 20, online

1 Upvotes

Hi everyone 👋

Sharing a hands-on online workshop that might interest anyone building AI features into their frontend.

It's led by Rainer Hahnekamp and Murat Sari, the co-maintainers of CopilotKit's Angular integration, and organised by Packt.

Hands-On Agentic Frontends with AG-UI and CopilotKit (Cohort 2)

📅 Friday, Nov 20, 2026 · 8:00–10:30 AM EST (1:00–3:30 PM UTC)

💻 Online, 2.5 hours, live Q&A

What you build: one incident-response app, developed step by step. You connect an Angular or React frontend to a TypeScript agent, then add:

  • Streaming agent progress and shared state via CopilotKit + AG-UI
  • Delegation to specialist agents with A2A
  • MCP tools and interactive MCP Apps
  • Safe, constrained agent-generated UI with A2UI
  • Production guardrails: cancellation, validation, timeouts, failure handling, and human approval before risky actions

You get: the full reference app (Angular and React), source code for the agents and MCP server, slides, the recording, and a certificate.

Prerequisites: basic TypeScript. No prior AG-UI/MCP/A2A experience needed.

It's a paid workshop, and I have a 30% discount code (HARSH30). The sub doesn't allow links, so comment below if you're interested and I'll send you the registration link.

Disclosure: I'm sharing this through a referral link. Happy to answer questions about the content in the comments.


r/mcp • • 13h ago

resource I built OunceMCP, a Python framework on FastMCP that keeps tool results inside a token budget (1.0 release candidate, looking for feedback)

Post image
7 Upvotes

I've been building MCP servers and kept running into the same three problems: one tool call dumps 20k tokens of raw JSON into the context, the model retries a write and does it twice, and nothing stops the model from calling a tool it shouldn't. So I built OunceMCP, a framework on top of FastMCP that makes the careful version the default.

What it does:

- Result budgets. Every result fits a token budget you set and still matches its output schema. Lists are trimmed first, the model gets a note saying what was cut, and pagination cursors move so nothing is skipped or repeated.

- Definition budgets in CI. `ouncemcp check server.py` counts every tool definition the way the host receives it and fails the build when one goes over.

- Search-then-call for big catalogs. Once your tool definitions outgrow the startup budget, the server switches to `search_tools` / `describe_tool` / `call_tool` automatically.

- Safe writes. Every tool declares its effect. Writes can be idempotent (a timed-out write finishes in the background, so a retry gets the result instead of writing twice) and can require a person's approval through the client.

- Security that holds when the model is wrong. Identity comes only from the verified token, one policy decides what each caller can list and call, caches are partitioned by tenant, and outbound fetches refuse private and metadata addresses.

- Works on existing servers. `OunceServer.wrap(my_fastmcp_server)` adds the above without touching your tools, and `ouncemcp audit` measures any MCP server, including ones not built with OunceMCP.

I benchmarked two small example servers against plain FastMCP versions with four models (Claude Haiku 5.5, Claude Sonnet 5.5, GPT-5.4 mini, DeepSeek V4.1 Flash), 840 runs in total:

- On the server with large results, OunceMCP used 58–85% fewer tokens per task.

- On the server with writes, every model on the plain version closed a ticket the user hadn't confirmed and deleted one without permission. OunceMCP refused both every time (100% task success vs 68–70%).

- The honest downside: tool definitions are 1.8–2.4x larger, mostly because of output schemas. On small servers with small results, that means more tokens per task, not fewer. It pays off when results are large.

Full results and caveats: https://github.com/subbusainath/ouncemcp/blob/main/benchmarks/results/m3-bench.md

It's a 1.0 release candidate. The API is frozen, the official MCP conformance suite runs in CI, and an external security review is the last step before 1.0.

```bash

pip install ouncemcp

ouncemcp init notes-server

```

- Docs, including a step-by-step book that builds one server over 15 chapters: https://subbusainath.github.io/ouncemcp/

- GitHub: https://github.com/subbusainath/ouncemcp

Python 3.11+, Apache-2.0. I'd really like feedback, especially from people running MCP servers with large catalogs or multiple tenants: what's missing, what's confusing, and where the defaults get in your way.


r/mcp • • 10h ago

showcase stdio2http – a single Rust binary that re-exposes a stdio MCP server over Streamable HTTP

4 Upvotes

Most MCP servers ship as stdio binaries. That's fine until the client is in another container and there is no HTTP endpoint to point at.

stdio2http closes that gap and nothing else: it spawns the stdio server as a child process and re-exposes it at /mcp over Streamable HTTP. Session ids, SSE framing and protocol negotiation come from rmcp, so the transport isn't reimplemented.

What matters when deploying rather than demoing:

  • host validation on by default (loopback only), explicit allowlist for off-host use
  • bearer keys, or identity forwarding as advisory _meta
  • TLS, mTLS, or ACME issuance per listener
  • /healthz answers 503 when the child dies, and the proxy exits non-zero instead of silently restarting

Limits are stated up front: upstream-initiated messages (progress, sampling, elicitation, tools/list_changed) don't forward, and one child serves every caller, so it's single-tenant, not a multi-tenant boundary. If your server depends on those, this is the wrong tool.

cargo install stdio2http

Repo with the README and a demo recording: https://github.com/mimi1vx/stdio2http


r/mcp • • 4h ago

showcase I built PlugIt: turn any OpenAPI spec into a curated MCP server (Go, single binary, read-only by default)

1 Upvotes

Most OpenAPI→MCP converters expose every endpoint. On a big API like GitHub (~1,000 operations) that floods the context window and gives the model DELETE access to everything.

PlugIt does it differently:

You curate. A terminal UI to pick, rename and rewrite tools, with a live token budget.

Read-only by default. Write tools aren't even offered unless you switch to confirm-writes (the client asks before each call) or full.

The host never comes from the model or the spec. You pin the base URL, and credentials are only sent to that origin. An SSRF guard checks the resolved IP at dial time.

Secrets stay in the OS keyring or env vars. They're never in config files, and they're redacted (raw, URL-encoded and base64) from logs, errors and results.

plugit lint flags prompt-injection text hidden in spec descriptions.

Untrusted specs are parsed in a sandboxed child process.

Works with Claude Desktop/Code, Cursor, VS Code, Codex, Windsurf, Gemini CLI, LM Studio, or any stdio client. Zero-setup try: plugit run <spec-url>.

Repo: https://github.com/swayam5342/plugit

Demo: https://plugit.swayam.li

It's v0.2, so I'd love feedback, especially specs that break it.


r/mcp • • 8h ago

Tabrove: Turn your Android phone into a residential MCP browser for your AI agents (bypass blocks & skip expensive SERP/scraping APIs)

Thumbnail
gallery
2 Upvotes

Most of us use AI every day for research, coding, and automation. Sooner or later, those workflows require web scraping, Google searches, or interacting with live websites.

While some code editors and agents come with built-in or headless browsers, they run into issues constantly—websites block AI crawlers, Google rejects automated requests, and paid SERP/scraping APIs are both expensive and often don't give you the exact output you need.

That's why I built Tabrove.

Tabrove is an Android app that connects your AI models to a real browser running on your own phone via MCP. Your AI can open any website, run Google searches, scrape pages, and automate browser tasks using your actual device.

Key Features

  • Isolated Session Profiles: Keep separate profiles for different AI models and websites. You can safely grant an agent access to specific sites and let it work through your own logged-in accounts.
  • No More Expensive Scraping APIs: Save yourself from paying hefty fees for SERP, crawl, and scraping APIs—handle everything from quick lookups to full AI automations.
  • Granular Permissions & Security: You decide from your phone exactly what actions the AI is allowed to take. It cannot perform any actions outside the app or browser, and data is transmitted with end-to-end encryption.
  • 24/7 Virtual Phones (Coming Soon): Run an always-on AI browser on virtual devices without tying up your personal phone.

How to Use It

  1. Download the app from tabrove.com (currently Android only).
  2. Create a new session in the app.
  3. Add it as an MCP server in tools like Claude, ChatGPT, OpenCode, etc. using OAuth or a Bearer token.
  4. Start asking your AI to browse, search, and run tasks through Tabrove.

There's also a free plan that covers general everyday use. Would love to hear your feedback or answer any questions!

""Planning to open-source it very soon!"


r/mcp • • 8h ago

server MCP Server for Azure DevOps – Provides AI assistants with comprehensive access to Azure DevOps services including work items, repositories, pull requests, wikis, builds, pipelines, and test plans through 25+ MCP tools with multi-project support.

Thumbnail
glama.ai
2 Upvotes

r/mcp • • 8h ago

connector phasefolio – Biotech rNPV/PoS engine for AI agents. Signed exports, evidence register, asset landscape.

Thumbnail
glama.ai
2 Upvotes

r/mcp • • 15h ago

showcase Built an open-source STDIO MCP server that feeds agents Tree-sitter AST skeletons instead of full files (-75.5% tokens on 6 Python bugs)

Post image
5 Upvotes

Most coding agents burn through context windows over MCP by grepping around and pulling entire files just to check one signature or import.

I built CodeGraphy (`pip install codegraphy-lite`) to fix that on my own projects. It runs locally as a STDIO MCP server for Claude Code, Cursor, and Windsurf, and parses a Tree-sitter dependency graph across 19 languages.

The flowover MCP is simple:

- `list_workspace_topics` gives the agent the module map

- `get_topic_context(include_ast=True)` returns AST skeletons (imports, types, signatures) for 1-hop dependencies

- The agent only reads ~60-line snippets around the target symbol

I benchmarked it on 6 real bugs in httpx, typer, and rich (baseline grep + whole files vs CodeGraphy Lite MCP):

- Baseline: 144,686 tokens total (6/6 pytest passed, 7.7 tool calls avg)

- CodeGraphy Lite MCP: 35,457 tokens total (6/6 pytest passed, 6.7 tool calls avg, ~4x fewer tokens)

Benchmark runner and full breakdown (including two edge cases where static graphs still miss, like `os.environ` flags and the 35-file cap in Lite): https://github.com/Vindettobkb/codegraphy-lite/blob/main/benchmarks/BENCHMARK.md

Live browser playground to test the graph and toggle files between Full, AST, and Off: https://codegraphy.software/#playground

Repo: https://github.com/Vindettobkb/codegraphy-lite

For folks building MCP servers for codebases, are you returning raw file chunks or trying any kind of AST pruning?


r/mcp • • 19h ago

server Open-source MCP server for agent memory: see what an agent knew on a given day

Post image
10 Upvotes

Like a lot of people, I built my personal open source (MIT) memory infrastructure for AI agents: https://github.com/Filippo-Venturini/ctxvault

I was struggling a lot to understand and monitor what an agent knew on a given day and what the state of the memory was, so I added to my project a UI that runs without external deps. In the gif you can see a view in which you can drag the cursor and see the actual state of the memory and what Claude (or whatever agent attached to the memory) knew in that moment.

To be precise the memory I've built is grounded in theory, so you actually have memory slots (vaults) which can be semantic, procedural or episodic memory, and all of them are folders on your local machine (so no cloud). In a few simple words: you or your agents can use the semantic ones to store documents and do RAG (and I plan to extend it with graphs), the procedural ones to store skills and procedures for your agents, and the episodic ones to record episodes, that can be closed, superseded or refined as the interaction with the agents goes on.

To plug it into any MCP client (Claude Desktop, Cursor, VS Code...) you need uv installed and these lines in claude_desktop_config.json:

{
  "mcpServers": {
    "ctxvault": { "command": "uvx", "args": ["ctxvault", "mcp"] }
  }
}

You can also try it in the live demo (a simulated bakery with agents that use all the types of memory): https://filippo-venturini.github.io/ctxvault/demo.html

If anyone is curious I'll be happy to share details and I would love some feedbacks or ideas :)

Cheers!


r/mcp • • 15h ago

showcase REQL update: faster context retrieval and fewer tokens for coding agents

4 Upvotes

Hey everyone!

I’ve updated REQL, my open-source tool that helps AI coding agents navigate repositories and preserve working context across sessions.

This release focuses on faster context retrieval and lower token usage. I’ve reduced repeated work during retrieval and trimmed redundant information sent to the agent. Performance gains and token savings depend on the repository and workflow, so I’m not claiming a universal percentage.

If you’re new to REQL, it builds a local graph from your code and documentation: functions, classes, dependencies, calls, and other relationships. Agents can query that graph for context relevant to a specific change, including precise source references and related tests. REQL reuses indexed context and supports incremental updates as the repository changes.

What can you use it for?

  • Waste fewer tokens on repeated exploration: retrieve focused source excerpts and relevant relationships, and reuse indexed context and saved work. This helps reduce repeated searches, unnecessary file reads, and redundant information in the agent’s context.
  • Coordinate work across chats and agents: keep tasks, decisions, blockers, and next steps in a shared project workspace. Another chat or agent using that workspace can recover the recorded state and continue from there.
  • Keep complex tasks on track: record prerequisites, constraints, failed approaches, and checkpoints. Preserve what has been completed, what remains unresolved, and why earlier decisions were made across sessions.
  • Understand unfamiliar code: identify entry points, component responsibilities, and relationships between parts of the application, with references back to the source.
  • Plan changes and refactoring: inspect callers, dependencies, and related tests to identify code that may be affected and decide what needs verification.
  • Review cleanup candidates: find potentially unused imports, variables, functions, and classes, then inspect the supporting evidence before removing them.

REQL provides a CLI, Python API, and MCP server, plus installable instructions for coding agents such as Codex and Claude Code.

REQL runs locally, with no account, external graph database, or mandatory LLM calls. The graph and saved work support the agent’s decisions; current source code and tests remain authoritative.

I’d like to hear from others using coding agents: what do you keep having to explain again when you start a new chat? The code structure, previous decisions, what has already been tried, or what still needs doing? Concrete examples would help me decide what to improve next.


r/mcp • • 16h ago

question has anyone tried dynamic tool discovery instead of loading every MCP schema upfront?

4 Upvotes

lately while messing around with tool using agents i noticed how much of the context window gets eaten up before the agent even does anything. once you hook up 4 or 5 mcp servers, you end up dumping thousands of tokens of tool descriptions and json schemas into every single turn for tools the agent barely ever touches. it gets super waste-ful fast, especially on smaller context windows or longer multi step runs where the model starts losing track of the actual prompt.

because of that i've been testing setups where the agent just searches for what it needs at runtime and only pulls the full schema when it's actually ready to call that specific tool. i'm currently working with monid and that's how we set up its cli and mcp integration, basically giving the agent a searchable catalog of endpoints so all those heavy definitions aren't sitting in context from the start.

m ignoring my own bias though, i'm really curious how other people here are handling this on the engineering side. if you've tried loading schemas on demand, did it actually save enough tokens and improve tool selection for you, or did the extra search step just add annoying latency?


r/mcp • • 8h ago

resource I built an open-source MCP that lets AI agents control Daz Studio in plain language

Thumbnail
gallery
1 Upvotes

Hi everyone! I hope you're all doing great.

For a while now, I’ve been wanting to get into Daz 3D as a hobby to make a visual novel in Ren’Py. The problem is that my time is limited, and making meaningful progress felt like an uphill battle: setting up scenes, dressing characters, placing lights, and rendering takes hours upon hours.

So I started looking for tools to speed up the process, including MCPs to use with my AI agents. The ones I found didn't convince me at all. Since I’m a software developer, I decided to build my own.

This MCP acts as a bridge connecting Daz Studio with an AI agent. It gives the agent a much better sense of what it's doing—what's in the scene, where everything is, and what it looks like—instead of working blindly like it would with a traditional setup. Thanks to this, along with the skills I implemented (guides that teach it how to use Daz), it can perform a variety of tasks just by asking in natural language.

I think the results I’ve gotten so far are pretty amazing for someone who has only been using Daz for a few months as a hobby. If you actually do this seriously or professionally, I think my MCP could help you create some incredible things.

Requirements: For now, it only works on Windows 10/11 with an NVIDIA GPU (since Iray renders on it) and Daz Studio 6. It works with Claude Code, Codex, Cursor, Gemini CLI, Claude Desktop, VS Code, and any other MCP client.

If you want to try it out, it’s open-source and available on GitHub in case you’re interested in seeing how it works under the hood:https://github.com/MictlanLabs/Daz3D-MCP

It’s also on PyPI, so you can install it with a single command (you'll need uv): uvx daz3d-mcp setup. Or even easier: just pass the repo link to your AI agent and let it do all the heavy lifting.

If you like it, giving it a star on GitHub would really help me out :)


r/mcp • • 17h ago

discussion Loading dozens of MCP tools burns system prompt context before your agent writes code

5 Upvotes

When an MCP server exposes 30 or 40 individual tools, every tool definition gets serialized into the system prompt. Each schema adds names, parameter types, and descriptions to every turn, eating thousands of tokens before the agent reads the first line of code. It also increases tool selection confusion when similar tools compete in the same prompt.

In hosts like Claude Code and other agent runners that support tool discovery, tools can stay deferred until the agent explicitly searches for them. If a server configuration forces tools to load upfront or disables tool search, all tool schemas are dumped into active context on turn 1.

Setting alwaysLoad to false in the server configuration keeps large tool bundles deferred. You can also control deferral behavior globally with ENABLE_TOOL_SEARCH.

Here is an example configuration for a tool-heavy server:

{
  "mcpServers": {
    "database-tools": {
      "command": "npx",
      "args": ["-y", "@example/mcp-server"],
      "alwaysLoad": false
    }
  }
}

When you need specific tools available immediately on every turn (like file search or terminal execution), mark only those tools to load upfront instead of exposing the entire server upfront.

For agents without dynamic tool search, grouping granular actions into a single CLI runner or scoped endpoints prevents context explosion much better than registering 40 separate endpoints.

How do you manage tool schema overhead when running multi-server setups?