V2EX MCP integration for AI agents.
Connect AI agents to V2EX through 13 structured actions, including get current member, create token, delete notification, and boost topic. Review authenticat…
- ACTION CONTRACTS
- 13
- 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 V2EX integration exposes
The V2EX Agent App exposes 13 provider-backed actions for social and developer tools work. Its current contract lets an authorized agent fetch the authenticated v2ex member profile, create a new v2ex personal access token from an existing token, and delete one v2ex notification by its numeric identifier. 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 V2EX account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real V2EX capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_memberREADFetch the authenticated V2EX member profile.
create_tokenWRITECreate a new V2EX Personal Access Token from an existing token.
INPUTS: scope / expiration
delete_notificationHIGH IMPACTDelete one V2EX notification by its numeric identifier.
INPUTS: notification_id
boost_topicREVIEWBoost one of the authenticated member's V2EX topics to the homepage.
INPUTS: topic_id
get_current_tokenREADFetch metadata for the V2EX Personal Access Token used by this connection.
get_nodeREADFetch a V2EX node by node name.
INPUTS: node_name
get_topicREADFetch a V2EX topic by numeric identifier.
INPUTS: topic_id
list_hot_topicsREADFetch public hot topics from the V2EX legacy JSON API.
list_latest_topicsREADFetch public latest topics from the V2EX legacy JSON API.
list_node_topicsREADFetch topics from a V2EX node.
INPUTS: node_name / p
list_notificationsREADFetch the latest V2EX notifications for the authenticated member.
INPUTS: p
list_topic_repliesREADFetch replies for a V2EX topic.
INPUTS: topic_id / p
INPUT CONTRACTS
Know what the action needs before it runs.
create_token
scopeREQUIRED- The access scope for the new V2EX token.
expirationREQUIRED- The token lifetime in seconds.
delete_notification
notification_idREQUIRED- The V2EX numeric identifier.
boost_topic
topic_idREQUIRED- The V2EX numeric identifier.
get_node
node_nameREQUIRED- The V2EX node name, such as `python`.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current Member
Fetch the authenticated V2EX member profile. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_memberControl Create Token
Create a new V2EX Personal Access Token from an existing token. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_tokenVerify with Get Current Token
Fetch metadata for the V2EX Personal Access Token used by this connection. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_tokenSAFETY BOUNDARY
Operate V2EX with explicit limits
- Authorize V2EX with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_notification` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in V2EX rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the V2EX task completed successfully.
CONNECTION MODEL
API key
V2EX Personal Access Token used as a Bearer token for API 2.0 requests. Create or manage tokens from your V2EX token settings.
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
- 9
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
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 V2EX.