Reporters.io
Investiga periodistas, medios de comunicación y referencias de artículos indexadas con un asistente compatible con MCP. Mantén visibles los enlaces a las fuentes; revela los contactos disponibles solo si se solicitan explícitamente.
Documentación
Reporters.io for AI agentsProfessional plan
Reporter research for your AI assistant.
Find journalists, research media outlets, and explore article evidence with Claude Code, Cursor, or Codex. Connect your assistant to Reporters with one API key.
One API key for REST and MCP. An active Professional subscription is required.
11 research tools · REST + MCP · Agent skills
Media research tools
Find reporters. Understand outlets. Review coverage.
Give your assistant structured research tools that connect a topic to journalist profiles, publication context, and indexed article evidence.
Discover relevant journalists
Search by topic, beat, and geography. Inspect profiles and contact availability before deciding who fits your story.
Explore media outlets
Find publications, inspect outlet details, and discover current accepted relationships between outlets and reporters.
Ground your research in sources
Use indexed article titles, dates, and links to explain a match. Reveal eligible reporter or editorial contacts when explicitly requested.
MCP connection
One endpoint. Your Reporters API key.
Connect over Streamable HTTP. Your client initializes the connection, discovers tools, and sends your API key with each request.
POSThttps://reporters.io/api/mcp
Authorization: Bearer <YOUR_API_KEY>
Content-Type: application/json
Accept: application/json, text/event-stream
Connect the client you already use.
- Claude Code, Cursor, and Codex configurations
- Hosted Streamable HTTP endpoint
- Private Bearer API key authentication
- Same Professional account as REST
Use a client that supports a private authorization header. The hosted server uses API keys; OAuth sign-in is not offered.
MCP repository and local bridge
Client setup
Connect Reporters to Claude Code, Cursor, or Codex.
Create a key in your dashboard, set it in your client’s environment, and copy the matching configuration.
Merge this server into your project’s.mcp.json. Set REPORTERS_API_KEY in the environment that launches Claude Code, approve the server, then check its connection with /mcp.
{
"mcpServers": {
"reporters": {
"type": "http",
"url": "https://reporters.io/api/mcp",
"headers": {
"Authorization": "Bearer ${REPORTERS_API_KEY}"
}
}
}
}
Set REPORTERS_API_KEY in your client’s environment before connecting.
Your key includes all API permissions and has no automatic expiration. API and MCP calls require an active Professional subscription.
Your first research task
From an API key to a useful shortlist.
- 01
Create your API key
Activate Professional, open API keys, and give your key a recognizable name. Store the value in your client’s environment. Open API keys - 02
Connect and discover
Add your client configuration. Ask your assistant to check account access and list the available Reporters tools. Choose your client - 03
Research and review
Search for a topic or publication, compare profiles, and inspect article evidence. Request contact details only for the records you choose. Try an example prompt
Example prompts
Ask your assistant to research the media.
Start with a concrete topic, publication, or selected profile. These prompts guide discovery and keep contact reveals deliberate.
Find journalists for a story
“Use Reporters to find journalists covering climate technology in the US. Review their profiles and indexed article links, then give me a source-linked shortlist explaining each match. Keep contact reveals separate until I choose a reporter.”
Research a publication
“Use Reporters to find a technology publication, review its profile, and inspect its affiliated reporters and indexed article links. Explain who covers my topic, with sources. Ask before revealing any newsroom contacts.”
Prepare a contact request
“For the reporter I selected, check the current profile and available coverage. If contact information is available, ask me to confirm that I want it revealed. After confirmation, retrieve the eligible contact and summarize the research context.”
Agent skills
Give your agent a research playbook.
Install reporter-research to guide discovery, profile review, article evidence, and deliberate contact reveals. Use it with MCP or the included Python REST fallback.
Explore the reporter-research skill
npx skills add ricciflow-api/reporters-agent-skills --skill reporter-research
The installer requires Node.js 22.20 or later. Configure your Reporters API key separately. The Python fallback requires Python 3.9 or later.
FAQ
MCP questions, answered.
Practical answers about access, available data, and getting started.
Which AI clients can connect?
Claude Code, Cursor, and Codex can connect using the configurations above. Other clients need Streamable HTTP support and a private Authorization header. Reporters does not offer OAuth sign-in for MCP.
Do MCP and REST use the same key?
Yes. Create one named key in your dashboard and use it for REST and MCP. All supported API permissions are included, and the key has no automatic expiration. Revoking it stops both integrations.
Which subscription do I need?
API and MCP require an active Professional (Pro) subscription. Free and Connect plans do not include access. The public setup pages and documentation can be read without subscribing.
Can my assistant retrieve contact information?
Yes, through an explicit contact-reveal tool for a selected reporter or outlet. Search and profile tools do not include private contact values. The example workflows ask for your intent before revealing contacts.
What does the agent skill add?
The reporter-research skill provides workflow instructions for discovery, evidence review, and deliberate contact reveals. MCP provides the callable tools. The skill also includes a Python REST fallback.
Is there a local MCP option?
Yes. The public reporters-mcp repository includes an optional Node.js stdio bridge. Clone the repository, install its pinned dependencies, and configure the local entry point. It forwards requests to the same hosted API and requires your Professional account and key.