MCP marketplace

Jobo for Composio

Live job search in your agents' toolbox.

Composio gives agents a managed set of tools and handles each user's authorization. Jobo is not in Composio's public catalog, but Composio lets any project register a remote MCP server as its own custom toolkit. Registered that way, Jobo's job search server appears to your agents like any other toolkit, and each user connects with their own Jobo account through Composio's connect link.

Composio logoComposioRegister the toolkit
typescript
import { Composio } from "@composio/core";

const composio = new Composio();

const toolkit = await composio.customToolkits.create({
  name: "Jobo Job Search",
  mcpUrl: "https://jobs-mcp.jobo.world/mcp",
  authSchemes: [
    {
      mode: "DCR_OAUTH",
      discoveryUrl:
        "https://enterprise.jobo.world/.well-known/oauth-authorization-server",
    },
  ],
  userId: "all",
});

console.log(toolkit.slug);

What can you do with the Composio integration?

Register Jobo's job search server as a custom MCP toolkit in your Composio project and hand it to your agents.

01

A toolkit like any other

Once registered, the server's tools are discovered by your agents through Composio's tool search, next to the rest of the toolkits in the session.

02

Per-user authorization

Each end user signs in to Jobo through Composio's connect link. Searches are billed to the account that signed in.

03

OAuth with dynamic registration

Jobo's authorization server supports dynamic client registration, which is the OAuth mode Composio's custom MCP toolkits use. There is no client ID to request.

04

Read-only tools

Every tool on the server reads job data. There is nothing an agent can change or delete through it.

How do you connect Composio to Jobo?

One-time setup. After this, the data keeps itself current.

  1. 1

    Register the server as a custom toolkit

    Call the custom toolkits API from the Composio SDK. The discovery URL is Jobo's authorization server metadata, not the MCP host. Setting userId to "all" shares the toolkit with every user in the project.

    typescript
    const toolkit = await composio.customToolkits.create({
      name: "Jobo Job Search",
      mcpUrl: "https://jobs-mcp.jobo.world/mcp",
      authSchemes: [
        {
          mode: "DCR_OAUTH",
          discoveryUrl:
            "https://enterprise.jobo.world/.well-known/oauth-authorization-server",
        },
      ],
      userId: "all",
    });
  2. 2

    Add the toolkit to a session

    Pass the slug the call returned in the toolkits list when you create a session for an agent.

  3. 3

    Have each user connect

    Send the user through Composio's connect link. They sign in with their Jobo account in the browser and approve access.

  4. 4

    Ask for jobs

    “Find remote staff engineer roles posted this week and list the employer and link for each.” The agent finds the Jobo tools through tool search and cites the listings it used.

What goes wrong with Composio, and how do you fix it?

The things people actually hit when running Jobo in Composio.

Creating the toolkit returns 403
A toolkit private to one user needs Composio's Pro plan. A shared toolkit, with userId set to "all", works on every plan.
The URL or auth settings need to change
Composio does not allow the MCP URL, auth schemes or user to be edited after creation. Delete the toolkit and create it again.
New tools do not show up
Composio does not resync a custom toolkit automatically. Sync it again when the server's tools change.

How do you get the most out of Composio?

  • Use a shared toolkit for a product with many users, so each of them connects their own Jobo account.
  • Tell the agent to include the listing URL for each role. Every real result has one.
  • Keep result counts small while exploring. Search bills per job returned; reading a single listing is free.

Start pulling live jobs into Composio

One Jobo account covers every integration, and the same job index sits behind all of them.