Skip to main content

Connect an assistant to Bytes

Bytes can connect to compatible assistants and MCP clients without asking you to copy a workspace API key into them.

The supported remote connection address is:

https://api.jaww.ws/mcp

Which clients can I use?​

ChatGPT and Claude have been production-verified with Bytes.

Bytes also identifies Cursor, Perplexity, GitHub Copilot / VS Code, Windsurf, Gemini CLI and JetBrains AI Assistant as compatible MCP clients. These clients support the remote MCP connection pattern Bytes uses, but Bytes-specific production verification has not yet been completed for them.

Compatibility does not mean a marketplace listing, partnership or endorsement, and client setup screens can change independently of Bytes.

ChatGPT​

ChatGPT has been production-verified against the Bytes remote MCP endpoint.

To use Bytes from ChatGPT:

  1. Open ChatGPT's controls for adding a remote MCP connection.
  2. Add https://api.jaww.ws/mcp as the connection address.
  3. Follow the Bytes sign-in and authorisation flow that ChatGPT opens.
  4. Choose the Bytes workspace you want ChatGPT to use.
  5. Review the requested permissions and approve the connection.
  6. Return to ChatGPT and use the available Bytes tools in your conversation.

The exact ChatGPT labels and placement of connection controls can change independently of Bytes. The supported Bytes endpoint and authorisation flow remain the same.

Direct MCP connection is supported now. Bytes is not currently published in the OpenAI Plugins Directory, which is a separate distribution channel.

Claude​

Claude has been production-verified against the Bytes remote MCP endpoint with delegated workspace access.

To use Bytes from Claude:

  1. Open Claude's controls for adding a remote MCP connection.
  2. Add https://api.jaww.ws/mcp as the connection address.
  3. Follow the Bytes sign-in and authorisation flow that Claude opens.
  4. Choose the Bytes workspace you want Claude to use.
  5. Review the requested permissions and approve the connection.
  6. Return to Claude and use the available Bytes tools in your conversation.

The exact Claude labels and placement of connection controls can change independently of Bytes. The supported Bytes endpoint and authorisation flow remain the same.

Set up another compatible connection​

If your assistant or MCP client lets you add a custom remote MCP server:

  1. Add https://api.jaww.ws/mcp as the server address.
  2. Follow the Bytes sign-in screen opened by the client.
  3. Choose the workspace you want that assistant to use.
  4. Review the permissions it is asking for.
  5. Choose Allow connection only when the workspace and permissions are correct.

The connection is then limited to the workspace and permissions you approved.

What an assistant can access​

The current assistant connection can work with supported:

  • Links
  • Activity Groups
  • Tags

Depending on the permissions you approve, it can read those records and can create or change Links and Tags.

Analytics and Offline Engagement are not part of the current assistant tool set.

Workspace roles and permissions​

Your current Bytes workspace role still applies when an assistant is connected.

  • Owner, Admin and Member roles can use the supported read and write permissions.
  • Viewer is read-only.

If your role changes later, Bytes applies the new role to the existing connection. For example, changing a Member to Viewer removes write access without waiting for the original connection to expire.

Review connected assistants​

Open Profile & Preferences > Security > Connected assistants to see active assistant connections.

For each connection you can review the client, workspace, approved permissions and recent use information when available.

Revoke access​

Choose Revoke access next to the connection you want to remove, then confirm it.

The assistant loses access immediately. Revoking an assistant does not revoke your workspace Developer API keys and does not sign you out of Bytes.

Common problems​

I approved the wrong workspace​

Revoke the connection and connect again. Select the intended workspace during the new approval flow.

The assistant cannot create or change anything​

Check both the approved permissions and your current role. Viewer access is always read-only. A connection approved with read access only will not expose write tools even for a write-capable workspace role.

A connection that worked before now fails​

The connection may have been revoked, your workspace membership or role may have changed, or the client may need to reconnect after an OAuth refresh problem. Reconnect through the assistant or MCP client if its normal refresh does not recover.

The client asks me for a Bytes API key​

Do not paste a Developer API key into a prompt or tool argument. The supported hosted connection uses Bytes sign-in and OAuth at https://api.jaww.ws/mcp instead.

For technical connection details, see the Bytes MCP developer guide.

Last updated on