external-content-providers-mcp
v0.3.2
Published
MCP server for internet content retrieval providers: Jina, markdown.new, defuddle.md, and SocialData.tools.
Maintainers
Readme
external-content-providers-mcp
MCP server for internet content retrieval providers:
r.jina.ai: read public URLs as LLM-friendly text, with optional Jina engine/proxy/cache controlss.jina.ai: search the web and convert results to LLM-friendly textmarkdown.new: convert public URLs to Markdowndefuddle.md: convert public URLs to clean MarkdownSocialData.tools: retrieve public X/Twitter tweets, users, timelines, mentions, and search results
Install
Run directly with npx:
npx -y external-content-providers-mcpExample Codex config:
codex mcp add external_content -- npx -y external-content-providers-mcpTools
content_provider_catalogjina_read_urljina_searchjina_auth_statusmarkdown_new_read_urldefuddle_read_urlread_url_markdownsocialdata_auth_statussocialdata_requestsocialdata_search_tweetssocialdata_get_tweetsocialdata_get_tweets_by_idssocialdata_get_user_profilesocialdata_get_user_tweetssocialdata_get_user_mentions
API Keys
Basic r.jina.ai, markdown.new, and defuddle.md URL reads can work without API keys.
Jina Search (s.jina.ai) and Jina proxy controls require a Jina API key:
export JINA_API_KEY="..."SocialData.tools requests require a SocialData API key:
export SOCIALDATA_API_KEY="..."On macOS, the server also checks Keychain entries with account codex:
security add-generic-password -a codex -s JINA_API_KEY -w "..."
security add-generic-password -a codex -s SOCIALDATA_API_KEY -w "..."For backward compatibility, the server also checks SocialData.tools and
SOCIALDATA_TOOLS_API_KEY Keychain service names.
The server never returns API keys from auth-status tools.
Notes
Some upstream endpoints have limited access or require paid/API-key access. The MCP server returns upstream HTTP status and error bodies where possible.
License
MIT
