How to Use the Zeplo (Queue & Background Job API) MCP in Claude Code

Q: How do I debug Zeplo (Queue & Background Job API) jobs in Claude Code?

Run listqueuelogs to pull a paginated history of every job executed. You can also use getrequest if you need the specific timeline for one failed run.

Q: What is the process for setting up background jobs with Zeplo (Queue & Background Job API) using Claude Code?

First, your script needs credentials via createtoken. Then, it calls enqueuerequest to push the payload onto the queue. The job runs completely headless in your environment.

Q: Can Zeplo (Queue & Background Job API) manage team access in Claude Code?

Yes. You use inviteteammember from the terminal to add users to a workspace. This is useful when setting up CI/CD pipelines that require multi-user access.

Q: Does the Zeplo (Queue & Background Job API) handle data privacy in Claude Code?

This MCP Server touches HTTP request payloads. Since it runs in a dedicated pipeline, all data handling is confined to the queue and scheduled job system.

Q: How do I list all available schedules with Zeplo (Queue & Background Job API) in Claude Code?

Run listschedules to get a full manifest of active jobs. If you need to change the timing, use updateschedule, or if it's finished its cycle, delete it with deleteschedule.

Run scheduled tasks and background jobs with Claude Code: Your headless terminal agent for CI/CD pipelines.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Zeplo (Queue & Background Job API) MCP to Claude Code

Create your Vinkius account to connect Zeplo (Queue & Background Job API) to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Zeplo (Queue & Background Job API) with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Control job flow from the shell

You can manage entire workflows directly in your script. Use `create_queue` to set up a new isolated environment, then run jobs using `enqueue_request`. This makes it perfect for automated pipeline steps.

Audit and maintain job infrastructure

Keep track of everything with `list_queues` or check the details of one specific task via `get_queue`. The ability to run `update_queue` means you can pause or resume jobs on the fly.

Secure and manage credentials

Don't hardcode tokens. Run `create_token` once, and your script uses that secure token for all subsequent calls to this MCP Server. You can also list existing tokens with `list_tokens`.

Setup guide

Set up Zeplo (Queue & Background Job API) MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see zeplo-queue-background-job-api-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Zeplo (Queue & Background Job API) transactions." It will automatically discover and invoke the available Zeplo (Queue & Background Job API) tools.

Terminal

claude mcp add --transport http zeplo-queue-background-job-api-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Zeplo (Queue & Background Job API) MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "zeplo-queue-background-job-api-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Zeplo. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Zeplo (Queue & Background Job API) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Zeplo (Queue & Background Job API) MCP in Claude Code

Run `list_queue_logs` to pull a paginated history of every job executed. You can also use `get_request` if you need the specific timeline for one failed run.

First, your script needs credentials via `create_token`. Then, it calls `enqueue_request` to push the payload onto the queue. The job runs completely headless in your environment.

Yes. You use `invite_team_member` from the terminal to add users to a workspace. This is useful when setting up CI/CD pipelines that require multi-user access.

This MCP Server touches `HTTP request payloads`. Since it runs in a dedicated pipeline, all data handling is confined to the queue and scheduled job system.

Run `list_schedules` to get a full manifest of active jobs. If you need to change the timing, use `update_schedule`, or if it's finished its cycle, delete it with `delete_schedule`.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript