connect your AI

Claude web or Desktop

1. Open Claude's Customize → Connectors (some versions place Connectors in Settings).
2. Choose Add → Add custom connector. Enter BytesSkills and the server URL above.
3. Keep OAuth authentication. Connect and complete BytesSkills email sign-in and consent. If prompted for OAuth client details, choose automatic registration rather than entering a secret.
4. Enable the connector in your conversation and try the verification prompt below.

Team or Enterprise administrators may need to add the connector for the organization first. Each user then signs in individually. For a remote connector, use this interface rather than editing Desktop's local-server configuration.

Claude's current connector instructions

Claude Code

Run in a terminal with Claude Code installed:

claude mcp add --transport http --scope user bytesskills https://api.bytesskills.com/mcp

Then open /mcp inside Claude Code and authenticate BytesSkills. This is a user-level connection on that machine. Check claude mcp list before adding it again.

Claude Code MCP documentation

let an agent help

Copy this prompt into your agent. It can configure supported tools; you complete sign-in and consent. If it cannot access settings, it should guide you through the manual steps.

Read https://bytesskills.com/docs/install.md and help me connect BytesSkills to this AI client. Reuse an existing connection if present, let me complete OAuth sign-in, and verify access with a read-only tool call.

# Connect BytesSkills

Configure this user's AI client to use the remote MCP endpoint:
https://api.bytesskills.com/mcp
Transport: Streamable HTTP. Authentication: OAuth through the client.

First identify the client: Claude web/Desktop, Claude Code, or another MCP host.
Inspect existing connections before adding one; reuse a matching BytesSkills endpoint.
Do not overwrite an unrelated connection with the same name or replace existing config.

For Claude Code with an available CLI, inspect with claude mcp list. If absent, run:
claude mcp add --transport http --scope user bytesskills https://api.bytesskills.com/mcp
Then have the user open /mcp in Claude Code and authenticate BytesSkills.
User scope makes the connection available across that user's projects on this machine.

For Claude web/Desktop, use Customize > Connectors > Add custom connector.
Name: BytesSkills. URL: https://api.bytesskills.com/mcp.
Use OAuth sign-in. If the client needs registration, use automatic registration.
If you cannot change connector settings, explain these exact manual steps.
The user must complete email sign-in and review consent themselves. Use the same
BytesSkills email as on their other devices to reach the same workspace.
Never ask for an owner key, email login link, password, or access token in chat.
Do not copy credentials between devices or commit them to a repository.

After authorization, inspect available BytesSkills tools and call bytes_workspace
once to verify workspace access. For help, call bytes_begin with command /bytes help
and a fresh UUID request_id. Do not create or modify an artifact just to test setup.
Report the verified workspace and any missing tools; do not claim success based only
on a saved config. If tools are absent, explain how to enable/reconnect the connector.

/bytes is conversational shorthand, not a guaranteed native slash command.
The user can instead say: Use BytesSkills to show help or find my saved artifacts.
Other clients must support remote Streamable HTTP MCP and OAuth. Use their supported
configuration interface; if unavailable, give manual steps rather than inventing one.

check the connection

Use the BytesSkills connector to check which workspace I am signed into, then show BytesSkills help. Do not create anything.

/bytes is conversational shorthand. A client may not register it as a slash command; ordinary language works when the connector tools are enabled.

• No BytesSkills tools? Enable the connector for the conversation, reconnect if needed, and try a new chat. A saved connection alone does not prove authorization succeeded.
• Wrong or empty workspace? Check that you signed into BytesSkills with the same email used on your other device.
• Sign-in expired? Start a fresh connection flow. Do not reuse an old authorization URL or email link.
• Missing tools after an update? Use the host's supported refresh or reconnect flow. Report the missing tool names rather than inventing an action.

For other AI hosts, use their remote HTTP MCP configuration with OAuth. No Git clone, owner key, or shared API token is required. Connection setup does not install computer-control or image-generation capabilities into a host that lacks them.