PR Agents on Medialyst

Medialyst gives your agent the data: real-time news search and journalist enrichment, over REST and the MCP server. That's the layer underneath the work — every result grounded in live coverage and real, recent bylines, not model memory.

There are two ways to build on it.

Use newsjack.sh (the full agent)

newsjack.sh is the open-source PR agent built on Medialyst. It's the smoothest way to put Medialyst to work from Claude, ChatGPT, Cursor, or your own terminal — opinionated skills for the whole PR loop, not just raw tool calls.

• Open source: github.com/elvisun/newsjack
• OAuth device login: run newsjack login, approve the browser prompt, and you're connected — no API key to copy out of the terminal.
• The full loop: find angles from live news, build a fit-scored journalist list, and draft pitches — with review and sending kept human-in-the-loop.

Reach for newsjack.sh when you want a working PR agent out of the box instead of assembling the primitives yourself.

Build your own agent (the primitives)

Prefer to wire Medialyst into your own agent? Point any MCP-capable client at the server and call the ten REST-backed tools:

https://medialyst.ai/api/mcp

• get_credit_balance → GET /api/v1/credits/balance
• lookup_article → GET /api/v1/articles/lookup
• lookup_articles → POST /api/v1/articles/lookup:batch
• lookup_publication → GET /api/v1/publications/lookup
• lookup_publications → POST /api/v1/publications/lookup:batch
• search_news → POST /api/v1/news/search
• query_pr_calendar → POST /api/v1/pr-calendar/query
• list_journalist_moves → GET /api/v1/journalist-moves
• enrich_journalists → POST /api/v1/journalists/enrich
• get_journalist_enrichment_job → GET /api/v1/journalist-enrichment-jobs/:jobId

The eleventh hosted tool, list_journalist_requests, is MCP-only. Async media-list creation (POST /api/v1/media-lists:create-async) and its job poll (GET /api/v1/jobs/:jobId) deliberately remain REST-only.

A few rules keep agents honest:

• Use journalist_reference for a known journalist. name requires at least one of publication, domain, or a real identifying url.
• Use article_url for a real article from search_news or the user when enriching its author. Never invent URLs.
• Use query_pr_calendar for planning moments, awareness days, conferences, and pitch timing.
• Use lookup_article for one known article URL and optional Markdown; use lookup_articles for 1-10 URLs without Markdown.
• Use lookup_publication for one outlet or article URL. lookup_publications accepts 1-25 cached/default URLs, or at most five with force_refresh: true.
• Budget 0.1 credit per successful article URL and 0.01 credit per successful publication URL. Per-URL failures cost 0 credits.
• All four lookup tools require media_lists:manage.
• Use fit_context.pitch on enrich_journalists when you want scored fit or pitch angles.
• enrich_journalists is async-only: it returns a job id; poll get_journalist_enrichment_job until the job is complete or failed.
• Use returned ids. Do not invent enrichment job ids.
• The MCP can't create media lists, read workflow rows, create share links, or send outreach. Review and sending stay in the Medialyst app, where the person whose reputation is on the line keeps final judgment.

Canonical known-journalist input:

{
  "from": [
    {
      "type": "journalist_reference",
      "name": "Jane Doe",
      "publication": "The Daily Example"
    }
  ]
}

See Medialyst MCP for OAuth and API-key setup, the full tool surface, and troubleshooting.