MCP

For users: connecting an MCP client to the Venture Network lets it read your profile, search the network, and act as you, all through the same account and permissions you have on the web and in the CLI. There is one permission model behind all three surfaces.

Connect

claude mcp add --transport http venture-network https://venturenetwork.ai/mcp

That one command registers the server for Claude Code. The first tool call opens the consent screen in your browser, where you sign in and choose which scopes to grant. For claude.ai, Cursor, the consent flow, the reconnect rule, and the full tool list, see MCP tools.

Scopes

Each scope shows up as a checkbox on the consent screen with this text, and lets a connected client do the following:

Scope	Consent screen text	What it lets a client do
profile	See your name and email	Read your basic identity.
network:read	Read your profile and the network	Read your own profile, list and search organizations and members, list an org’s invitations.
network:write	Update your profile on your behalf	Update your profile, join an organization, invite someone to one you admin, revoke an invitation.
offline_access	Stay connected without signing in again	Keeps the connection working without a fresh sign-in every time.
admin	Manage members and invites	Approve or suspend a member, promote or demote, create and list invite codes. Needs both the admin scope and an admin role on your account.

openid is always granted, its checkbox disabled, because the flow needs it to identify you. profile is checked by default like the other scopes, but you can uncheck it if the client does not need it. Accept only what the client actually needs.

Example prompts

• “List the organizations in the Venture Network and tell me which ones I belong to.”
• “Find members who are founders with the skill react and summarize what they are looking for.”
• “Update my headline to say I am looking for a technical co-founder.”