io.veezeePublished by veezee.ioOfficial publisherv3.1.0Updated Oct 24, 2026
LinkedIn data for AI agents: search, profiles, companies, posts. Free key, self-minted, no signup.
The publisher's own server: All
Overview
Hosted MCP server that gives an assistant LinkedIn data — URL resolution, profiles, people search, companies and posts — plus optional Reddit and X mounts.
- What you can do
- Resolve LinkedIn URLs and fetch person profiles, with optional extra sections
- Search people and look up company pages
- Read recent posts by a person or company
- Optionally cover Reddit and X on the same server: search, subreddits, users, posts and tweets
- Check remaining credits and recent charges with get_usage
- When to use it
- Useful when an assistant needs LinkedIn research — qualifying people, mapping companies, or pulling recent posts — and you would rather use a hosted endpoint than scrape yourself. The combined mount suits research briefs or monitoring loops that span LinkedIn, Reddit and X.
- Requirements
- Remote streamable-http endpoint; no local runtime needed, though a stdio proxy is offered for clients that spawn a command. Every call needs a Veezee API key, sent as an Authorization bearer header or obtained through the OAuth sign-in flow. A free trial key can be minted without signup; the free tier is 200 credits per IP per day.
Installation
In SourceWeft
- Open Linkedin in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.veezee%2Flinkedin/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"linkedin": {
"type": "http",
"url": "https://mcp.veezee.io/linkedin"
}
}
}README
Veezee MCP server
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.
- Every call needs a free key, and minting one costs nothing: no signup, no card, no human. See Quickstart below. The free tier is 200 credits per IP per day across all platforms, cached data, first page only. Paying at https://veezee.io/upgrade credits the same key with a higher budget, realtime freshness, and full pagination.
- Website and docs: https://veezee.io
- Found a bug or a gap? Open an issue or write [email protected].
Run locally (stdio)
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.
Mounts
Four endpoints, all streamable-http, same auth and pricing:
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.
The 17 tools
LinkedIn (https://mcp.veezee.io/linkedin)
Reddit (https://mcp.veezee.io/reddit)
X, formerly Twitter (https://mcp.veezee.io/x)
Every mount
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
Quickstart
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.
Install
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
REST twin
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).
Links
- Agent setup guide: https://veezee.io/agent-setup/prompt.md
- Operating rules for agents: https://veezee.io/AGENTS.md
- Pricing: https://veezee.io/pricing
- What we store and how keys are handled: https://veezee.io/trust
- Skills packs: https://github.com/veezeehq/veezee-skills
Source: README.md at commit 6d6c715
Tools
0Version history
1- v3.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Veezee integrations
All
io.veezeeOfficial publisher
Hosted MCP server giving AI assistants real-time LinkedIn, Reddit and X (Twitter) data through 17 lookup and search tools.
X Twitter
io.veezeeOfficial publisher
Hosted MCP server that gives an assistant read access to X (formerly Twitter) posts, profiles and search results.
io.veezeeOfficial publisher
Hosted Veezee MCP endpoint that gives an assistant read access to Reddit posts, comments, subreddits, users and search results.