FeedSheriff MCP
Last updated October 3, 2026
What this is
Hosted Model Context Protocol server at https://feedsheriff.com/mcp. Paid Solo or Multi plans can let Claude, ChatGPT, Cursor, VS Code, Codex, and other agents read the dashboard, write filters, and (if you turn it on) run cleanups.
Most clients sign in with OAuth in the browser. Cursor and scripts can use an API key from Settings β AI Agents. Cleanup is a separate scope and needs a preview confirmation before any mail moves.
Fastest path
Paste one line into your agent. It reads feedsheriff.com/SKILL.md, adds the MCP server, and walks you through OAuth (or your API key if you pasted one).
Pick your agent
Connect Claude Code
- 1Open Claude Code in your project.
- 2Paste the line below and press Enter.
Set up https://feedsheriff.com/SKILL.mdNo key needed for OAuth clients. Cursor and scripts can use a key from Settings β AI Agents.
Endpoint
- Skill:
https://feedsheriff.com/SKILL.md - MCP:
https://feedsheriff.com/mcp(Streamable HTTP) - OAuth metadata:
https://feedsheriff.com/.well-known/oauth-protected-resource
Cursor
Settings β MCP β add this, then complete OAuth:
{
"mcpServers": {
"feedsheriff-mcp": {
"url": "https://feedsheriff.com/mcp"
}
}
}Or install the plugin from github.com/sarthakguptadev/feedsheriff-mcp and paste a key if asked. Skills in that repo teach the agent how to draft filters, preview cleanups, review mail, and undo.
Claude Code
claude mcp add --transport http feedsheriff-mcp https://feedsheriff.com/mcp
Run /mcp and finish OAuth. For skills and slash commands:
/plugin marketplace add sarthakguptadev/feedsheriff-mcp /plugin install feedsheriff-mcp@feedsheriff-mcp
Claude Desktop / Claude.ai
Add a custom connector with URL https://feedsheriff.com/mcp, or the same JSON as Cursor in claude_desktop_config.json. Complete OAuth when prompted.
ChatGPT
Settings β Apps & Connectors β add a custom MCP connector.
- Server URL:
https://feedsheriff.com/mcp - Auth: OAuth
Approve read, write, and (optionally) cleanup in FeedSheriff. Your ChatGPT plan must allow custom connectors.
Codex
[mcp_servers.feedsheriff-mcp] url = "https://feedsheriff.com/mcp"
Put that in ~/.codex/config.toml, then codex mcp login feedsheriff-mcp.
VS Code
{
"servers": {
"feedsheriff-mcp": {
"type": "http",
"url": "https://feedsheriff.com/mcp"
}
}
}Save as .vscode/mcp.json, then Command Palette β MCP: List Servers β start β OAuth.
Windsurf, Gemini, and others
Point any Streamable HTTP MCP client at the same URL. If the client only supports local stdio:
{
"mcpServers": {
"feedsheriff-mcp": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://feedsheriff.com/mcp"]
}
}
}API key
Send the key as a Bearer token. Keys start with fs_live_ and are shown once. Create one in Settings. After you create it, Settings shows a one-line prompt that already includes the key.
{
"mcpServers": {
"feedsheriff-mcp": {
"url": "https://feedsheriff.com/mcp",
"headers": {
"Authorization": "Bearer fs_live_YOUR_KEY"
}
}
}
}Skills
/SKILL.md is the onboarding skill: add MCP, auth, and safety rules. The plugin repo ships workflow skills so the agent uses tools in the right order: status, draft a filter, preview then start a cleanup, review uncertain mail, undo. Same pattern Notion and AnyAPI use: MCP for access, skills for the workflow.
Tools
Read: account, mailboxes, dashboard, filters, routines, activity, review queue, live scans. Write: draft, test, create, update, and delete filters; update routines; decide review. Cleanup: preview, start, undo.
Email sender and subject are marked untrusted. Starred and important mail is never moved. Every action can be undone for 30 days.
