Listen Notes for AI agents
Listen Notes is a podcast search engine and database used to discover and pull data on podcasts and episodes worldwide. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Listen Notes.
Search for a podcast episode
Search episode titles for a topic to find relevant podcasts, a read-only lookup.
Pull details on a podcast
Retrieve a podcast's details and episode list before including it in a roundup.
Get recommendations for an episode
Pull episode recommendations related to one already reviewed to round out a playlist, a read-only suggestion lookup.
26 Listen Notes actions, graded by risk.
Every Listen Notes action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
18Look things up. Allowed by default.
- listen_notes.get_playlist_by_idFetch Playlist Info
- listen_notes.find_episodes_by_titleSearch Episode Titles
- listen_notes.fetch_podcast_languagesFetch podcast languages
- listen_notes.fetch_supported_regionsFetch Supported Regions
- listen_notes.fetch_related_search_termsFetch related searches data
- listen_notes.fetch_trending_search_termsRetrieve trending searches
- listen_notes.fetch_podcast_episodes_by_idFetch Podcast Details And Episodes
- listen_notes.fetch_a_list_of_podcast_genresRetrieve genre list
- listen_notes.fetch_a_list_of_your_playlistsGet playlists
- listen_notes.fetch_a_random_podcast_episodeListen to just listen endpoint
- listen_notes.fetch_curated_lists_of_podcastsGet curated podcasts
- listen_notes.fetch_recommendations_for_a_podcastGet podcast recommendations by id
- listen_notes.fetch_recommendations_for_an_episodeGet episode recommendations by id
- listen_notes.fetch_a_curated_list_of_podcasts_by_idRetrieve curated podcast by id
- listen_notes.fetch_a_list_of_best_podcasts_by_genreFetch best podcasts list
- listen_notes.fetch_audience_demographics_for_a_podcastGet podcast audience by id
write
7Create and change things. Allow, or ask the user first.
- listen_notes.full_text_searchSearch operation endpoint
- listen_notes.typeahead_searchGet typeahead suggestions
- listen_notes.spell_check_on_a_search_termSpell check retrieval
- listen_notes.refresh_rss_feed_of_a_podcastPost podcast rss by id
- listen_notes.batch_fetch_basic_meta_data_for_episodesPost episodes by ids
- listen_notes.batch_fetch_basic_meta_data_for_podcastsCreate podcast via form data
- listen_notes.submit_a_podcast_to_listen_notes_databaseSubmit podcast rss url
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- listen_notes.request_to_delete_a_podcastDelete podcast by id
Listen Notes in three steps.
- 01Your users connect Listen NotesThey add their Listen Notes api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “search operation endpoint” can wait for the user, and “delete podcast by id” can be denied outright.
- 03Any agent can actYour agent calls Listen Notes through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('listen_notes', { read: 'allow', write: 'ask', // full_text_search destructive: 'deny', // request_to_delete_a_podcast }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Listen Notes connects.
Users add their Listen Notes api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Listen Notes connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Listen Notes from any agent.
Listen Notes and Arc0, answered.
Can I use Listen Notes with Claude, ChatGPT or Cursor?
Yes. Connect Listen Notes to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Listen Notes actions you allow.
How do users connect Listen Notes?
Users add their Listen Notes api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Listen Notes actions can my agent take?
26 in total: 18 read, 7 write and 1 destructive, such as “search operation endpoint”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Listen Notes?
Yes. Actions like “delete podcast by id” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Listen Notes too?
Yes. The same Listen Notes connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Listen Notes into your agent.
Your users connect Listen Notes once, under your brand. Your agent gets 26 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan