NexusToken

Create/check agent tasks, discover capabilities, and run V2 Jobs on NexusToken.

NexusToken is an MCP server that connects AI agents to the NexusToken platform. It is distributed as a Python package on PyPI (version 0.6.5) and communicates over stdio transport. Two environment variables are required at runtime: NEXUS_API_KEY for authentication and NEXUS_BASE_URL to point the client at the correct NexusToken endpoint.

The server’s stated scope covers three areas. First, agents can create and check the status of agent tasks on NexusToken, allowing a workflow to submit work and later retrieve results. Second, agents can discover what capabilities are available on the platform, which supports dynamic decision-making about what operations to invoke next. Third, agents can run V2 Jobs, enabling execution of structured job workloads through the NexusToken job runtime.

Because no individual tool definitions were published with this server record, the exact parameters and return shapes of each operation are not documented here. Developers should consult the repository at github.com/bobuilds/nexustoken-sdk for the current API surface.

This server is appropriate when an agent needs to interact programmatically with the NexusToken platform specifically. It is not a general-purpose task queue, job runner, or database connector, and it has no relevance to workflows that do not involve NexusToken.

Use cases

  • Submit agent tasks to NexusToken and poll for their completion status.
  • Discover available capabilities on the NexusToken platform before deciding which operation to invoke.
  • Trigger V2 Jobs on NexusToken from within an automated agent workflow.
  • Integrate NexusToken job execution into a stdio-based MCP agent pipeline.

When to use it

  • The agent workflow targets the NexusToken platform specifically.
  • Tasks or jobs need to be created and monitored programmatically via an MCP-compatible agent.
  • Dynamic capability discovery against NexusToken is required at runtime.
  • The runtime environment supports stdio transport and can supply NEXUS_API_KEY and NEXUS_BASE_URL.

When not to use it

  • The workflow has no dependency on NexusToken — this server provides no general-purpose task or job management.
  • A transport other than stdio is required (e.g. HTTP SSE).
  • NEXUS_API_KEY or NEXUS_BASE_URL cannot be provisioned in the deployment environment.
  • Detailed tool-level documentation is needed before integration; no tool schemas are currently published in the registry record.