Medialyst
DevelopersMedialyst MCP

Medialyst MCP

Medialyst exposes a remote MCP server for agents that need to search news, create media lists, inspect media-list tables, update rows and columns, and create share links.

The site docs are for setup. The MCP server is the source of truth for agents while they work.

Endpoint

Production:

https://medialyst.ai/api/mcp

Local development:

http://localhost:3000/api/mcp

The server uses MCP Streamable HTTP with API-key auth:

Authorization: Bearer <MEDIALYST_API_KEY>

OAuth is not required for v1.

Required Scopes

Use the smallest key that covers the workflow:

ScopeNeeded for
news:searchSearching recent news coverage
media_lists:readListing, reading, and inspecting media lists
media_lists:writeCreating lists, mutating tables, deleting lists, and creating share links

Keep keys out of prompts

Store API keys in environment variables or your agent client's secret storage. Do not paste raw keys into a chat thread or commit them to a repo.

Runtime Docs Tools

Agents should not rely on stale copied schemas. After connecting, they should ask the MCP server how to use the current contract.

ToolPurpose
get_usage_guideCurrent workflow guidance by topic
get_tool_referenceCurrent tool examples, scope requirements, and optional generated schemas

Recommended first calls:

{
  "topic": "getting_started",
  "detail": "short"
}

Then, before a mutation:

{
  "tool_name": "apply_table_action",
  "detail": "full"
}

Use include_schema: true only when examples are not enough. Some table-action schemas are large.

Tool Surface

ToolScopeUse it for
get_usage_guideAPI key onlyRead current operating guidance
get_tool_referenceAPI key onlyRead examples and optional schemas
search_newsnews:searchFind fresh articles and bylines
create_media_listmedia_lists:writeCreate a list from articles, URLs, keywords, or empty state
list_media_listsmedia_lists:readFind existing lists
get_media_listmedia_lists:readRead metadata, columns, settings, and optional rows
inspect_tablemedia_lists:readRead bounded previews or enrichment health
read_full_valuesmedia_lists:readRead exact values for a small row/column slice
preview_column_rendermedia_lists:readPreview formula, AI, send, or template-bearing columns
apply_table_actionmedia_lists:writeMutate columns, cells, rows, views, run state, and article imports
create_share_linkmedia_lists:writeCreate public read-only share links
delete_media_listmedia_lists:writeDelete a list after explicit user intent

Agent Operating Model

Media lists are workflow tables. The table is the deliverable.

Good agents follow this pattern:

  1. Call get_usage_guide.
  2. Search or list existing media lists.
  3. Create or select a list.
  4. Inspect the table before edits.
  5. Use returned IDs from tool responses.
  6. Preview template-bearing columns before applying them.
  7. Apply one focused table action at a time.
  8. Verify with get_media_list or inspect_table.
  9. Share only when the user asks for a public link.

Fewer, better, evidence-backed

The agent should curate article results before creating rows. More rows are not automatically better. The goal is a focused list of journalists who actually cover the story.

Codex

Add this to ~/.codex/config.toml:

[mcp_servers.medialyst]
url = "https://medialyst.ai/api/mcp"
bearer_token_env_var = "MEDIALYST_API_KEY"

Then verify inside Codex:

/mcp

Claude Code

Claude Code can connect to HTTP MCP servers. A user-scoped setup looks like:

claude mcp add-json medialyst '{
  "type": "http",
  "url": "https://medialyst.ai/api/mcp",
  "headers": {
    "Authorization": "Bearer ${MEDIALYST_API_KEY}"
  }
}' --scope user

For rotating keys, use your client's dynamic header helper instead of hardcoding a header value.

Stdio-Only Clients

For OpenClaw and other MCP-compatible agents, use their remote HTTP MCP configuration when they can send custom headers. If an agent cannot connect to remote HTTP MCP servers or cannot send custom headers, bridge through mcp-remote:

{
  "mcpServers": {
    "medialyst": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://medialyst.ai/api/mcp",
        "--header",
        "Authorization: Bearer ${MEDIALYST_API_KEY}"
      ]
    }
  }
}

Example Workflow

Ask your agent:

Search recent AI infrastructure coverage, create a media list from the best articles, add a Notes column, and share the list.

Expected sequence:

  1. get_usage_guide
  2. search_news
  3. create_media_list
  4. inspect_table
  5. get_tool_reference for apply_table_action
  6. apply_table_action with create_column
  7. apply_table_action with patch_cells if notes are known
  8. create_share_link after the user asks to share

Troubleshooting

SymptomWhat to check
401 UnauthorizedThe key is missing, malformed, revoked, or not sent on every request
403 ForbiddenThe key is valid but lacks the required scope or fails an IP allowlist
402 Payment RequiredCredits or plan limits block the operation
Validation errorsCall get_tool_reference for the failing tool
Stale IDsCall get_media_list or inspect_table again
Client cannot attach headersUse the mcp-remote stdio bridge

Agent Skill

For open-source agents, use a small bootstrap skill that tells the agent how to connect and when to call the runtime docs tools. Keep detailed schemas on the server.

Install the Medialyst MCP agent skill.