Add your first account

Connect one OAuth or token-backed MCP server and verify its tool catalog.

From the console

Open a connection namespace, choose Add connection, and select a provider. Quick-add presets include Notion, Linear, GitHub, Slack, Sentry, Figma, Granola, Asana, and Stripe; any compatible remote MCP URL can be added manually.
Keep the suggested stable tool prefix or choose one before saving. For example, two Notion connections can become lelapa_notion__search and personal_notion__search.
Complete upstream consent separately for each connection. Each authorization is stored and refreshed independently.
Review the discovered tools, then grant the owning namespace to an MCP client or publish an eligible connection to a shared endpoint.

Choose the connection scope

Personal is visible only to its exact owner through a subject-bound client endpoint. A label such as “Personal” does not create this boundary; the stored scope and owner do.
Shared is workspace-owned and can appear on shared delivery surfaces. Operators need an explicitly delegated namespace to create one.
Service is an owner- or admin-created workspace credential for automation and can be placed on shared delivery surfaces.

Choose upstream authentication

Use a bearer token when the upstream issues one directly. For OAuth, prefer Dynamic Client Registration when the provider supports it; otherwise provide the upstream client ID, requested scope, and client secret when that provider requires one.

Figma OAuth

Choose the Figma preset and continue without entering a client ID, client secret, or scope. Synaxis discovers Figma's OAuth settings, requests the provider-advertised mcp:connect scope, registers dynamically, and completes authorization with PKCE.

Figma currently limits its remote MCP server to approved clients, and Synaxis is not listed in Figma's MCP catalog. Until Figma approves Synaxis, Figma may deny registration. The console shows that provider-approval error instead of reporting the Engine as unavailable. See the Figma MCP guide.

If you created Figma through the previous pre-registered flow, remove that connection and create it again. Reauthorize intentionally reuses saved static-client credentials and will not switch the connection to dynamic registration.