Your agent needs Glimyo’s server address. It can then discover how to sign in and request access.
01
Add Glimyo to your agent.
In your agent’s remote MCP or connector settings, add this server URL and choose OAuth authentication.
https://glimyo.com/mcp
Clients with dynamic registration can obtain a client ID automatically. No API key or client secret is needed.
02
Sign in. Choose its access.
Your agent opens a Glimyo sign-in page. Enter your SMS code there, review the agent’s callback address, and approve only the permissions you need.
Your SMS code stays on Glimyo. The agent receives its own limited access token.
03
Make something together.
Start with “Show me my products.” When you’re ready to create or edit, ask your agent to request the additional permissions.
Connections expire after 30 days. Review activity or revoke access any time in Connected agents.
PREFER TO ASK IN CHAT?
Give your agent this starting point.
This works only if the agent can configure remote MCP connections. Otherwise, use its connector settings.
Connect to Glimyo using its remote MCP server at https://glimyo.com/mcp. Read https://glimyo.com/agents.txt for setup instructions. Start with brand:read and products:read. Give me the Glimyo sign-in link so I can enter my SMS code and approve access myself. Never ask me to share my OTP or access tokens in chat.
A CLEAR SCOPE OF WORK
A helpful assistant. A workspace you control.
Read your brand & products
Give your agent context: brand voice, colors, product descriptions, and prices.
Read saved creations
Let it check headlines, captions, prompts, and generation status.
Create & edit drafts
Make brand templates and revise copy. Editing approved content returns it to draft.
Export images
Download saved creations as SVGs in square, portrait, or story sizes.
Paid AI generation and PNG downloads are available in the web studio. Agent access does not include publishing, approving content, account changes, your phone number, or provider keys. Revoking access stops future requests; it cannot recall data already received by the agent.
CONNECTION NOTES
Find your way in.
Protocol available
Remote MCP clients
Glimyo supports Streamable HTTP, OAuth authorization code with S256 PKCE, and dynamic client registration. These flows have been tested with Glimyo’s integration tests. Each agent’s actual connection still needs validation.
Client testing pending
Meta Muse & Muse Code
Muse has a connector platform. Muse Code documents MCP OAuth and dynamic registration. Glimyo has not been tested in either client or listed in Muse’s connector directory.
Instinct co-developed PACT, which uses a separate agent identity and delegation flow. Glimyo does not yet implement PACT or have a verified Instinct connection.
Open Connected agents, register the exact callback URL shown by your agent, and copy the client ID back into its settings. Use public-client authentication with no client secret. Sign in with the same Glimyo account that registered the client.
Manual setup remains available when automatic registration is unsupported or temporarily rate limited.
Request only needed scopes. Use the exact MCP resource URL in authorization and token requests. Let the human complete login and consent. After connecting, use tools/list for the schemas of permitted tools.
Public registration identifies a callback, not a verified agent. Glimyo supports server-side and native clients; cross-origin browser JavaScript and Client ID Metadata Documents are not currently supported.