The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Veezee MCP listing page.
LinkedIn, Reddit, and X (formerly Twitter) data for AI agents, over MCP or REST. This repo is the public home and issue tracker for the hosted servers on the official MCP Registry: io.veezee/linkedin (3.1.0), io.veezee/reddit (1.1.0), and io.veezee/x-twitter (1.1.0). The server is a hosted service; this repo also ships a small stdio proxy (npx github:veezeehq/veezee-mcp) for clients that spawn a local command.
For MCP clients that spawn a local command instead of connecting to a URL:
The proxy connects to https://mcp.veezee.io/all and mints a free trial key on first run (no signup). Set VEEZEE_API_KEY to reuse one key across runs, and VEEZEE_MCP_URL to point at a single-platform mount. Docker: docker build -t veezee-mcp . && docker run -i veezee-mcp.
Four endpoints, all streamable-http, same auth and pricing:
| mount | covers |
|---|---|
https://mcp.veezee.io/linkedin | LinkedIn only (5 tools + get_usage) |
https://mcp.veezee.io/reddit | Reddit only (6 tools + get_usage) |
https://mcp.veezee.io/x | X (formerly Twitter) only (5 tools + get_usage) |
https://mcp.veezee.io/all | Every platform (17 tools + get_usage) |
Pick a single-platform mount when your agent only needs one platform: a smaller tool list is easier for the model to pick from correctly and costs less context per turn. Pick /all when one task spans platforms, e.g. a research brief that pulls LinkedIn, Reddit, and X signal on the same account, or a monitoring loop that watches more than one platform at once.
LinkedIn (https://mcp.veezee.io/linkedin)
| tool | what it does | credits |
|---|---|---|
linkedin_resolve_url | identify a LinkedIn URL | 2 |
linkedin_get_profile | get a person profile | 4 base (2 sections included, +2/section, max 4) |
linkedin_search_people | search people | 10 base (10 results included, +1/10 more, max 30) |
linkedin_get_company | get a company | 4 base (+4 to resolve a new domain) |
linkedin_get_posts | recent posts by a person or company | 4/page (+4 to resolve a new domain) |
Reddit (https://mcp.veezee.io/reddit)
| tool | what it does | credits |
|---|---|---|
reddit_search | search posts, comments, subreddits, or users | 6/page |
reddit_get_subreddit | get subreddit details | 4 base (+2 for rules and moderators) |
reddit_get_subreddit_posts | get a subreddit's posts | 4/page |
reddit_get_user | get a Reddit user | 4 base (+2/section, max 2) |
reddit_get_post | get posts by id, with an optional discussion thread | 4 for up to 10 ids (+1/10 more, max 100; +4 for the full thread or one comment in context) |
reddit_resolve_url | identify a Reddit URL | 2 |
X, formerly Twitter (https://mcp.veezee.io/x)
| tool | what it does | credits |
|---|---|---|
x_search | search X (formerly Twitter) | 6/page |
x_get_profile | get an X profile | 4 |
x_get_tweets | get an account's tweets | 4/page |
x_get_tweet | get one tweet with full metrics | 4 |
x_resolve_url | identify an X URL | 2 |
Every mount
| tool | what it does | credits |
|---|---|---|
get_usage | check credits and recent charges | 0 |
Any tool call can set freshness: "realtime" for +2 credits to force a live fetch instead of cached data. Full tool reference with schemas: https://veezee.io/docs
Every tool call needs a key, and getting one costs nothing. Mint one directly:
That returns a vz_trial_... key with the same free-tier budget as before: 200 credits per IP per day, cached data, first page only. Drop it into your MCP client config as a bearer header, then reconnect. Example for /all (swap in /linkedin, /reddit, or /x for a single-platform mount):
Don't want to mint a key by hand first? If your client supports MCP authorization (Claude Code, claude.ai connectors), just connect: the server answers unauthenticated requests with a sign-in challenge and the client opens a Veezee sign-in in your browser (email code, no password, no card). Clients without that support get a KEY_REQUIRED error whose message spells out the mint step (POST /v1/keys/mint) plus a mint_url. Either route, you get from zero to a working connection with no signup form and no card.
Paying at https://veezee.io/upgrade credits the same key, trial straight to flex; nothing to reconfigure. Realtime freshness and full pagination come with a paid balance.
Examples below use /all; swap in /linkedin, /reddit, or /x for a single-platform mount.
Claude Code:
Codex CLI:
Cursor (.cursor/mcp.json or ~/.cursor/mcp.json):
VS Code (.vscode/mcp.json):
claude.ai: Settings > Connectors > Add custom connector > https://mcp.veezee.io/all (or a single-platform mount).
You can connect any of the clients above before you have a key: OAuth-capable clients sign in on first contact, and the rest get a KEY_REQUIRED error that spells out the mint step, as described in Quickstart; add the Authorization header once you have the key.
More clients (Windsurf, Cline, Zed, plain REST), each snippet verified against the client's official docs: https://veezee.io/docs/clients
Every tool has a REST route with identical semantics at https://api.veezee.io (contract: https://veezee.io/openapi.json). A typed TypeScript SDK and CLI ship as @veezee/sdk (docs: https://veezee.io/docs/sdk).