Use Meerkat in Claude.
Meerkat plugs into Claude as a custom connector. Once you sign in, Claude can talk to Meerkat the same way you do on getmeerkat.dev — back-and-forth chat, real drafts, the full voice. Meerkat is the brain; Claude is just the surface.
https://getmeerkat.dev/api/mcpThen in Claude → Settings → Connectors → Add custom connector → paste. Sign in with the email you use for Meerkat, click Allow, and you're done.
Once Meerkat is connected, Claude has five tools. The first two call straight into Meerkat's actual chat brain — the same engine that powers getmeerkat.dev. The other three give Claude direct access to your Meerkat shelf, so prompts you've saved on the web are available inside Claude and vice-versa.
chat_with_meerkatthe main moveMulti-turn conversation with Meerkat. Returns Meerkat's spoken reply, the current draft prompt, follow-up suggestions, a title, and (on refactor turns) a critique. Claude calls this every time you mention Meerkat or keep a Meerkat thread going. Auto-saves the conversation to your shelf.
refactor_promptone specific jobPaste an existing prompt and ask Meerkat to make it sharper. Returns the same structured output as chat_with_meerkat, plus a critique of what the original got right and what specifically was tightened.
search_shelfread-only · pullSearch your saved prompts on getmeerkat.dev by title or body. Use it when you reference something you already saved ("pull up my onboarding email prompt"). Returns the full prompt text so Claude can hand it back or pipe it into a refactor.
list_projectsread-only · scopeLists your Meerkat project folders so Claude can confirm one before filing a save into it ("save this to my Q4 launch project"). Returns id, name, and last-updated time for each project.
save_specimenexplicit saveOne-shot save to your shelf without going through a chat turn. Use it when you have a prompt in your hand — something you wrote, Claude wrote, or pasted — and you tell Claude "save this to Meerkat." Optional project_id files it into a folder.
Plain English does the routing. “Use Meerkat to write me a launch post,” “ask Meerkat to fix this prompt,” “pull my onboarding prompt from Meerkat,” “save this to my Meerkat shelf.” Claude picks the right tool, forwards the conversation, and renders Meerkat's reply in its voice instead of paraphrasing.
A few prompts that exercise each tool. Paste any of these into Claude after the connector is live.
chat_with_meerkat“Use Meerkat to help me write a prompt that turns meeting notes into a 3-bullet exec summary for my CFO.”
chat_with_meerkat· follow-up“Now ask Meerkat to make it more skeptical — the CFO is allergic to soft language.”
refactor_prompt“Have Meerkat refactor this: “You are a world-class marketing expert. Write me an engaging blog post about AI.””
search_shelf“Pull my onboarding email prompt from Meerkat.”
save_specimen“Save this to my Meerkat shelf so I can reuse it later.”
Meerkat only sees the inputs you (or Claude on your behalf) send to a tool call — the prompt text you want refactored, the messages in the Meerkat thread. We do not see the rest of your Claude conversation, your other connectors, or your Claude account.
We log enough to meter usage (which user made which call, when) but never the full text of refactored prompts. Read the full breakdown in our privacy policy.
Anytime, two ways:
Questions or corrections → support
ChatGPT Apps SDK build is in testing — same endpoint, same tools.