> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tokencraft.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace Resources

> Access workspace data through MCP resources

# Workspace Resources

MCP resources provide read-only access to your Tokencraft data. Clients can read workspace information directly without calling tools.

<Note>
  Resources are served by the hosted MCP server at `https://app.tokencraft.dev/api/mcp`.
</Note>

## Resource URIs

All resources use the `tokencraft://` scheme.

### List All Workspaces

```
tokencraft://workspaces
```

Returns all workspaces for the authenticated user.

### Workspace Tokensets

```
tokencraft://workspace/{workspace_id}/tokensets
```

Returns all tokensets in a specific workspace.

## Example Usage

### In an MCP client

The client automatically accesses resources when needed:

```
You: What's in my workspaces?

Assistant: [Reads tokencraft://workspaces resource]

           You have 3 workspaces...
```

## Resource Format

Resources return JSON data following the API response format:

```json theme={null}
{
  "workspaces": [
    {
      "id": "550e8400-e29b-41d4-a716-446655440000",
      "name": "Design System",
      "description": "Main product design system"
    }
  ]
}
```

## Dynamic discovery

The hosted server builds the resource list dynamically on each `resources/list` request. As you add workspaces and tokensets, new resource URIs appear automatically.

## See Also

* [Tokenset Resources](/mcp/resources/tokensets)
* [Token Resources](/mcp/resources/tokens)
* [MCP OAuth](/mcp/oauth) — authenticate to access resources