SShortSingh.
Back to feed

How to Design Focused MCP Servers When Your API Has Hundreds of Endpoints

0
·17 views

Large APIs with hundreds of endpoints pose a unique challenge for Model Context Protocol (MCP) server design, as exposing every endpoint in a single server overwhelms AI clients with too many similar tool choices. Unlike human developers, AI clients navigate APIs by scanning tool names, descriptions, and schemas, making noise and redundancy a significant obstacle to accurate responses. Experts recommend grouping endpoints by user workflow rather than by technical availability, creating separate focused MCP servers for functions like customer support, billing, and administration. This approach reduces the number of tools per client connection, simplifies permissions, and lowers the risk of an AI agent selecting an irrelevant or unsafe action. Splitting large APIs into workflow-specific MCP surfaces also makes testing, logging, and role-based access control more manageable.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

53ON: Open-source OpenAI-compatible AI server for AMD Ryzen AI Max mini PCs

A developer has released 53ON, an MIT-licensed AI server built for AMD Ryzen AI Max+ 395 mini PCs with 128 GB of unified memory. It runs as a dependency-free Node.js process on top of llama.cpp and supports both OpenAI and Anthropic API formats. The software includes a control panel for loading models, issuing per-client API keys with token quotas, and forwarding requests to cloud providers when local models fall short. The author also publishes a custom llama.cpp build whose KV cache allocates memory as tokens arrive, not all at load time, which reduces initial memory use substantially on Vulkan. So far it has been tested only on Strix Halo hardware with Vulkan (RADV) on Ubuntu 24.04, and the author invites feedback and bug reports.

0
ProgrammingDEV Community ·

Per-Account Timezone Scheduling for SaaS Deadline Emails Using UTC Dispatch

The article argues that SaaS systems should store each customer's timezone and local business deadline as data rather than encoding them in cron expressions. A single UTC scheduler resolves that local intent into an eligible instant and claims due records for delivery. Recalculation and rule versioning let pending work adapt to changes without altering already delivered emails. Because email side effects cannot realistically be exactly-once, the author recommends at-least-once execution paired with idempotent operations and a stable delivery identity. Ambiguous local times during clock transitions need an explicit, versioned, and tested resolution policy.

0
ProgrammingDEV Community ·

AllRatesToday Launches MCP Server to Give AI Agents Live Exchange Rates

AllRatesToday has released an MCP server that lets AI agents pull live currency data instead of relying on outdated training information. The service offers real-time mid-market rates for over 160 currencies, refreshed every 60 seconds. It also provides official rates from 123 central banks and six tax authorities, including historical data, plus commercial bank rates from 1,219 banks across 124 countries. The server works with clients such as Claude Desktop, Claude Code and Cursor, and the same data is available through a plain REST API for other agent frameworks.

0
ProgrammingDEV Community ·

Tenant-Scoped Retrieval Design for a Developer Changelog Tracker

The article argues that a healthtech changelog tracker should first decide whether a result is durable, citable tenant data or fresh public web information. It proposes a tenant-scoped vector index for internal changelogs, with web search reserved for explicitly live context, both behind a single retrieval contract. Tenant isolation is treated as a system invariant, with documents addressed by tenant, document ID, and revision, and tenant scope applied before ranking. The author describes failure boundaries so that a web timeout or vector store outage degrades gracefully without leaking data across tenants. Routing is recommended by explicit intent categories rather than model guesses, with separate timeouts, budgets, and idempotent consumers to keep the system operable at scale.