Sniffington for AI agents
Sniffington is a hosted social listening application with an MCP server at https://sniffington.com/mcp, on every plan. Claude and ChatGPT add it as a connector and sign in; coding agents add it in one line or one config block. Then your agent can read the feed, mark posts done and sniff any brand.
Claude
Add a custom connector and sign in.
Set it upChatGPT
Add a custom connector and sign in.
Set it upClaude Code
One command, then sign in.
Set it upCursor
One config block, then sign in.
Set it upCodex
One config block, then sign in.
Set it upGemini CLI
One config block, then sign in.
Set it upVS Code
One config block, then sign in.
Set it upCLI
npx sniffington: text or JSON.
Set it upGrokbot, Muse and other assistants
Use the same MCP address for a personal assistant or a team agent. Each connection uses the workspace and access you approve.
Grokbot
- Paste this into a chat with your Grokbot:
- Follow its connection steps. If it offers OAuth, sign in to Sniffington, pick your workspace and choose Read only. If it needs a key, create a separate read-only key under API keys and enter it in the connector's credential setup.
Add Sniffington as a remote MCP server at https://sniffington.com/mcp. It uses Streamable HTTP and supports OAuth sign-in or an Authorization: Bearer API key. Keep credentials out of the conversation. After connecting, call whoami to confirm the workspace and access, then get_brief. Ask before changing anything.Grokbot makes the new tools available from your next message. This is a custom MCP connection; Sniffington is not a built-in Grokbot plugin.
Grokbot's connector instructions
Muse
- Ask Muse to create a custom connector using this prompt:
- Let Muse guide the setup. Sign in to Sniffington if it offers OAuth, or create a separate read-only API key and enter it through Muse's secure credential setup.
Create a custom connector named Sniffington. Its public MCP endpoint is https://sniffington.com/mcp, using Streamable HTTP. It supports OAuth sign-in or an Authorization: Bearer API key. Store any key in your Secure Credentials Store, never in the conversation. After connecting, call whoami to confirm the workspace and access, then get_brief. Ask before changing anything.Ask Muse to save the connector for future chats. Meta does not review custom connectors.
Other assistants
- Choose a remote MCP server over Streamable HTTP and paste the server URL.
- Use OAuth sign-in if your assistant supports it. Otherwise create a separate API key and add it as the Authorization header below.
- Start with read-only access. Ask the assistant to call whoami, then get_brief, to check the connection.
Authorization: Bearer YOUR_SNIFFINGTON_API_KEYStore the key in the assistant's credential settings. Each assistant needs its own key or OAuth connection, so you can revoke access separately. Assistants that only accept local stdio or legacy SSE need a compatible bridge; this URL uses Streamable HTTP.
Sniffington's protocol and authentication are tested separately from these apps. These instructions follow the providers' documentation; we have not completed a connection inside Grokbot or Muse.
What your agent can do
get_brief | What needs attention today, most urgent first, with reasons |
|---|---|
sniff_brand | What people said about any brand this week, namesakes ruled out |
list_mentions | Filter and page the feed by brand, platform, sentiment, urgency or words |
update_mention | Mark a post done or follow-up, or correct the AI's call |
get_analytics | Totals, trends and the mix by platform and keyword |
create_project | Start tracking a new brand |
Built for a technical team? Sniffington for developer relations teams covers technical threads, bug reports and comparisons.
Plus every other operation in the API reference marked MCP tool. Sign in with OAuth, or send an API key as Authorization: Bearer ss_…; read-only keys only see read tools. MCP docs.
Playbooks for Claude Code
The Claude Code plugin ships a playbook for each routine job. Each one tells the agent which tools to call, in what order, and what to hand back to you. Install with /plugin marketplace add ankurmans/sniffington-mcp.
daily-triage | Work through today's mentions by urgency: reply, flag or close |
|---|---|
weekly-report | A one-page weekly summary with the posts that mattered |
crisis-check | Is something blowing up? Size it, find where it spreads, draft a reply |
clean-up-noise | Find which keywords bring noise and exclude what's behind it |
competitor-watch | Share of voice and the complaints that could win you customers |
reddit-opportunities | Threads worth joining, with honest help-first drafts you post yourself |
review-digest | What App Store reviewers praise and complain about |
Let your agent sign itself up
No account yet? Your agent can ask for one in your name. It sends your email address, you approve once from the link we email you, and it collects an API key. You pick the workspace, whether it can change things, and a daily budget for the actions that spend on data. You stay the owner, and to upgrade it asks for a payment link that you open and pay.
curl -X POST https://sniffington.com/api/agent/signup \
-H "content-type: application/json" \
-d '{"email":"you@example.com","agent_name":"Claude"}'
Reads are unlimited; a key's costly actions (new projects and keywords, scans, sniffs) stop at its daily budget. How it works.
Type your brand. See who's talking.
Free for one brand. Upgrade when it earns its keep.