get_feed_events — Homespun MCP Tool Read-only

get_feed_events (get feed events) is one of 26 tools on the Homespun MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call get_feed_events from your client

Claude Code Homespun get_feed_events run in your project directory
Claude Desktop Homespun get_feed_events ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Homespun get_feed_events ~/.cursor/mcp.json
VS Code Homespun get_feed_events .vscode/mcp.json
Zed Homespun get_feed_events ~/.config/zed/settings.json
Windsurf Homespun get_feed_events ~/.codeium/windsurf/mcp_config.json
Cline Homespun get_feed_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Homespun get_feed_events ~/.gemini/settings.json
Grok Homespun get_feed_events .mcp.json (in your project root)
ChatGPT Homespun get_feed_events Settings → Connectors → Advanced → Developer mode
Claude.ai Homespun get_feed_events Settings → Connectors → Add custom connector
LangChain Homespun get_feed_events pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http homespun https://homespun.dev/mcp

Other tools on this server

deploy_app
list_rows
count_rows
get_row
upsert_row
update_row
delete_row
list_deleted_rows
restore_row
apps
members
grants
transfer
credentials
connections
ingest
attachments
taste
key
feedback
agent
community
publisher
review
get_skill

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Homespun MCP server