JevMade

Sign in
← Back to experiments

Agent tooling

jev-mcp-router

Put Jev between an agent and its tool collection so the agent sees a smaller, task-specific menu.

Bookmark: jev-mcp-router Keep this in your collection.
Leave a noteWhat would you try with this? : jev-mcp-router

Only you can see your notes.

Source screenshot of jev-mcp-router
SOURCE SCREENSHOTFull screenshot ↗

What it does

Yes-or-no decisions narrow the list of servers, tools and playbooks. The shortlist reduces prompt clutter; it is not an authorization boundary.

How you can use it

If your assistant sees hundreds of tools, borrow this filter's approach: choose relevant tool collections first, then choose tools within them. Start with the supplied pretend tools before connecting real services. Real Jev choices need a provider access key; the offline keyword option only checks that the connections are wired up.

Keep permission checks in the tools themselves, outside the model's choices. The gateway can call a known tool even if it was left off the smaller menu. It also cannot ask for more tools after a miss. Test a task where the needed tool is missing before relying on the shortlist.

Your note

Only you can see this. Clear the text and save to remove it.

Keep what you save

Sign in to keep bookmarks and private notes on every device. We email you a link; there is no password, and the same link creates your account.