Getting started

From a fresh account to an agent making its first call takes about five minutes.

1. Create your account

Register with an email address and a password of at least 12 characters, then confirm your email from the link we send. Once you are in, you can add a passkey or an authenticator app under your account settings for stronger sign-in.

2. Create a workspace

Everything in ToolGlue lives inside a workspace: connections, tools, API keys, run history, and the money balance. Your first workspace is created during sign-up, and new workspaces start with a $1.00 welcome balance so you can try things without entering a card. You can invite teammates later from Settings; roles are Owner, Admin, and Member.

3. Connect your agent over MCP

Your workspace has one MCP URL. On this deployment it is:

https://toolglue.dev/mcp

There are two ways to let an agent in:

  • OAuth sign-in. Paste the MCP URL into a client such as claude.ai or Claude Desktop. The client registers itself, sends you to a sign-in and consent page, and you pick which workspace it may use. No key handling at all.
  • API key. Mint a key on the Keys page and give it to the agent as a bearer header. Best for Claude Code, Cursor, scripts, and CI. See API keys.

4. Mint an API key

Open Keys in the app, choose a name, tick the scopes the agent needs, and optionally set an expiry. The full key is shown exactly once, together with copy-paste snippets for the claude CLI and an mcp.json block. Store it somewhere safe; ToolGlue keeps only a hash.

5. Let the agent explore

A connected agent should start with the overview tool, which describes the workspace, then list_connectors and connect to wire up apps (the connect tool hands you a link to finish authentication in the browser), and act to make calls. Your dashboard shows balance, recent runs, and active builds as they happen.

Something went wrong on our side. Reload
Interactive features couldn't start. The realtime connection is being blocked. If this domain sits behind Cloudflare or a WAF, allow websockets to /_blazor. Retry