Meerkat is answering right now. Last checked 4 min ago.
A prompt engineer you talk to. It writes prompts, sharpens yours, and keeps them on your shelf.
Today is the operative word: we check Meerkat every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
claude mcp add meerkat --transport http https://getmeerkat.dev/api/mcp
{
"mcpServers": {
"meerkat": {
"url": "https://getmeerkat.dev/api/mcp"
}
}
}
[mcp_servers.meerkat]
url = "https://getmeerkat.dev/api/mcp"
{
"mcpServers": {
"meerkat": {
"url": "https://getmeerkat.dev/api/mcp"
}
}
}
{
"mcpServers": {
"meerkat": {
"url": "https://getmeerkat.dev/api/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://getmeerkat.dev/api/mcp | streamable-http | sign-in | 219 ms | 4 min ago |
Your PromptLikeEngineer prompt library as MCP tools, slash prompts and resources. Add-only saves.
Your agent writes a UAT. You walk it and pin problems. It reads and fixes them. You verify.
What you keep and where: money, things, notes. End-to-end encrypted; decrypts on your computer.
Publish pages your agent writes to a private, shareable URL, then read, comment on and update them.
AI software engineer — writes code, opens PRs, reviews code, generates tests, and more.
Your AI writes HTML; Envie renders it to video on your machine, verifies it and shows it back.
Ask the human for API keys in a browser page and write them to .env. The model only sees key names.
Notes your team and their agents build on together: write, share, comment and edit.
Answers built from our own checks of this server.