Mediastack MCP integration for AI agents.
Connect AI agents to Mediastack through 2 structured actions, including search live news and search news sources. Review authentication, inputs, workflows, a…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Mediastack integration exposes
The Mediastack Agent App exposes 2 provider-backed actions for data and social work. Its current contract lets an authorized agent search live mediastack news articles with optional keyword, source, location, and sorting filters and search mediastack news sources with language, country, category, and pagination filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Mediastack account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Mediastack capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
search_live_newsREADSearch live Mediastack news articles with optional keyword, source, location, and sorting filters.
INPUTS: keywords / sources / countries / languages / categories
search_news_sourcesREADSearch Mediastack news sources with language, country, category, and pagination filters.
INPUTS: search / countries / languages / categories / limit
INPUT CONTRACTS
Know what the action needs before it runs.
search_live_news
keywordsOPTIONAL- Keywords used to filter returned news articles by title or description.
sourcesOPTIONAL- Comma-separated source identifiers used to filter returned articles.
countriesOPTIONAL- Comma-separated country codes used to filter returned articles.
languagesOPTIONAL- Comma-separated language codes used to filter returned articles.
categoriesOPTIONAL- Comma-separated categories used to filter returned articles.
search_news_sources
searchREQUIRED- Search text used to match source names or descriptions.
countriesOPTIONAL- Comma-separated country codes used to filter the returned sources.
languagesOPTIONAL- Comma-separated language codes used to filter the returned sources.
categoriesOPTIONAL- Comma-separated categories used to filter the returned sources.
limitOPTIONAL- Maximum number of sources to return.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Search Live News
Search live Mediastack news articles with optional keyword, source, location, and sorting filters. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
search_live_newsVerify with Search News Sources
Search Mediastack news sources with language, country, category, and pagination filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
search_news_sourcesSAFETY BOUNDARY
Operate Mediastack with explicit limits
- Authorize Mediastack with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Mediastack data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Mediastack rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Mediastack task completed successfully.
CONNECTION MODEL
API key
Mediastack API key sent with the access_key query parameter. Find it in https://mediastack.com/dashboard.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Mediastack.