Show: I replaced 21 MCP tools with one generic http(method, path, body)

[rangersui]

Pre-submission Checklist

• This post follows the MCP community guidelines

What would you like to share?

I built an AI workspace with 21 MCP tools. Then I realized every tool was just an HTTP request to my own backend.

I replaced all 21 with one:
http(method, path, body) → forwards to localhost:3004

Backend adds a new route → AI can use it immediately.
No tool registration. No schema update. No MCP server restart.

The server never inspects content, same principle as transparent transmission in networking. AI writes strings. Browser renders them. Server just stores and forwards.

The MCP adapter is now 20 lines. What remains is a protocol:

1. Listen on a port
2. HTTP strings in/out
3. SQLite stores strings
4. HMAC signs strings
5. Browser renders strings

Code: https://github.com/rangersui/Elastik
~200 lines. MIT.

Curious if others have noticed this pattern: MCP tools converging toward generic HTTP forwarding. Is there a reason
to keep tool-level granularity, or does a single transparent proxy cover most use cases?

Relevant Links

https://github.com/rangersui/Elastik