Developer Access

Configure external clients, connected MCP servers, scopes, and tool policies.

Where to find it

Open Account > Assistant > Developer Access.

Address: /account/assistant?panel=developer.

Use this page

Configure Build or Workspace MCP, OAuth, fallback tokens, personal Drive/Calendar access, and connected MCP tool policy.

Choose the connection

Select Build MCP for private artifact-build workflows or Workspace MCP for permission-filtered context. Copy the configuration for that exact product, authenticate, and start with a read-only check. Review the scope and tool policy of connected MCP servers separately.

Understand checks

Check connection tests what Topline can inspect. It cannot certify another app's local client configuration. Personal Google connections belong in Profile where the sign-in return flow directs you.

Related guides

• Build MCP
• Workspace MCP
• MCP server comparison

Access, states, and recovery

Each product and connection has separate scopes; Check connection cannot inspect an external client's local configuration.

Controls and availability depend on the active account and your permissions. If a page is unavailable, verify account access before changing configuration.

Connected tools

Follow Connected tools and approvals for provider identity, Chat/Coding workflow access, selected agents, tool execution policies, scope changes, and one-time approvals. These settings are separate from configuring an external Build or Workspace MCP client.