Reelier MCP server
by seldonframeRecord what your AI agent did once, then replay it the same way every time and get a receipt.
AI Library · 4,611 MCP servers
Record what your AI agent did once, then replay it the same way every time and get a receipt.
Let your AI read log files, filter events by level or component, and summarize errors for you.
Lets your AI coding assistant pause and ask you for feedback before it calls a task done.
Let your AI create, list, inspect and delete webhooks on webhook-test.com for you.
Your AI writes illustrated user help articles from your code, with screenshots, and saves them as Markdown files.
Lets your AI run a health check on an AI agent before you put it to work.
Ask your AI to scan a codebase for dead code, circular imports, coupling, and architecture drift.
Lets your AI read your local code and answer questions about structure, calls, and change impact.
Teaches your AI how you actually use another MCP server, safely and read-only, so it stops guessing.
Give your AI a toolbox for domain, DNS, email, and web checks, plus handy developer utilities.
Lets your AI check, clean up and repair code files, JSON and text on your own computer.
Ask your AI to map out a system's structure, bottlenecks, and risks, with every answer backed by math.
Your AI can rank your code files by importance, map dependencies, and answer questions about your codebase.
Lets your AI check, tidy up, and scan SQL queries for problems before you run them.
Lets your coding AI look up functions, callers, and what breaks if you rename something, without grepping.
Lets your AI look up who calls a piece of code, what depends on it, and what breaks if you change it.
Lets your AI search and pull sections out of your local Markdown files, like wikis and guides.
Lets your AI scan a code folder and score how safe and production-ready it looks.
Lets your AI safely read files, query databases, and run approved commands in your local project.
Run several copies of the same MCP server side by side, each with its own name, settings and files.
Give your AI a map of your code so it can find who calls what, and what a change touches.
Let your AI review your codebase and suggest which tests to write next, with evidence.
Lets your AI read your project's own rule files so it follows your standards every time.
See when your long AI coding session is getting expensive and when it is time to start fresh.