Skip to main content

Glen MCP integration

AI utilities connector, available on Zeplik

Glen MCP is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Glen MCP and Zeplik can act on your AI for you: Access organizational memory and context from Glen through its official hosted MCP server, using the connected user's authorized Glen workspace. You stay in the conversation while the assistant does the work in Glen MCP directly.

Zeplik exposes 22 write actions for Glen MCP. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Glen MCP without your consent.

Try Glen MCP on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with Glen MCP

Act in Glen MCP (22)

Runs only after you enable write access.

  • Glen artifact create

    Save a document (Markdown or HTML+CSS, no JavaScript) to the org's artifact library. Private to you by default; pass shareWithOrg:true to make it visible to the whole org. Pass update:true to overwrite a same-named artifact you authored.

  • Glen artifact delete

    Permanently delete an artifact you authored, by its exact slug. Irreversible: only call when the user explicitly asked to delete that artifact, and confirm the slug with them first.

  • Glen artifact

    Fetch a saved artifact (document) from the org's artifact library by its exact slug. Returns the full content ready for use. Only artifacts you authored or that were shared with you are reachable.

  • Glen artifact search

    Find a saved document in the org's artifact library by intent or keywords. Searches artifacts you authored plus ones shared with you. Returns ranked candidates (slug, title, summary, author). Empty query returns the most recently updated artifacts.

  • Glen artifact share

    Share an artifact you authored: add teammates by email and/or set org:true to make it visible to the whole org (org:false turns whole-org visibility off). Additive: existing recipients are kept; removing someone is done in the dashboard's Share dialog.

  • Glen code search

    Trace specific lines of code back to the agent conversations that produced them. Use for "why is this code like this" or "who decided this". Run `git blame -w -M -C --porcelain -L <start>,<end> -- <path>` and pass the distinct commit SHAs (drop the all-zero SHA of uncommitted lines) as shas; read each commit's message and pass any `Glen-Conversation: <id>` trailer values as trailerConversationIds; pass the origin remote as repoUrl in the form https://<host>/<owner>/<repo> (lowercase host, no .git suffix, SSH remotes converted). Returns state no_anchor when no conversation is linked to those commits. For org-wide questions use glen_search instead.

  • Glen dependency search

    Search the org's existing dependencies (tools/runtimes a skill needs) before creating a new one, so you reuse a match instead of duplicating. Returns ranked candidates (id, name, kind, sourceUrl, description).

  • Glen feedback

    Send a bug report (kind:"bug") or product feedback (kind:"feedback") about glen itself to the Glen team. File bugs only for a concrete, reproducible glen malfunction. Set onBehalfOf:"user" when the user asked you to send it, "agent" when you are reporting it yourself; set proactive:true when the user never asked (refused while the user is off the record). Pass conversationId (your session id) so the team can open the transcript.

  • Glen forget

    Exclude one or more verified wrong, stale, or irrelevant evidence items from future Glen recall. Pass the observation:<id> and message:<id> references shown in search Sources unchanged. Multiple references may be submitted together when they repeat the same stale claim. Raw messages remain visible in transcript history. Never forget on suspicion alone; tell the user exactly what was forgotten.

  • Glen import

    Import one turn of a past coding-agent conversation into the org's shared memory. Only call when the user asked to import their old sessions. Send one call per turn, in order: messages is that turn's user message and the assistant reply, with each message's original occurredAt (ISO 8601). Use conversationId "import:<session id>" for every turn of a session, and idempotencyKey "<conversationId>:<turn index>" so a re-run skips turns already imported. Set additionalContext.agent.name (claude-code, codex, cursor, pi or jcode) and, when known, additionalContext.workspace (cwd, branch, repoName, remoteUrl). Secrets are redacted server-side; nothing is stored while the user is off the record.

  • Glen invite

    Invite one or more teammates by email to the active organization so they share its memory. role is member (default) or admin. Only org owners and admins can invite. Confirm the email addresses with the user before calling. Adding people to a paid plan charges each seat now, prorated.

  • Glen list orgs

    List the organizations the user belongs to; active:true marks the one this connection reads and writes. A tool can't switch orgs; the user reconnects to pick another (or runs `glen org switch` in the CLI).

and 10 more.

How to connect Glen MCP

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Glen MCP immediately.

  2. Connect Glen MCP

    Open Settings and go to Connectors, then press Connect on Glen MCP. You can also connect from the Glen MCP page in the app.

  3. Approve access to Glen MCP

    Approve access on Glen MCP's secure consent screen. You are returned to Zeplik and can start giving instructions that use Glen MCP.

Frequently asked questions

Can I use Glen MCP with Zeplik?
Yes. Glen MCP is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Glen MCP account inside any conversation.
What can Zeplik do with Glen MCP?
Once connected, Zeplik has 0 read and 22 write actions for Glen MCP. Access organizational memory and context from Glen through its official hosted MCP server, using the connected user's authorized Glen workspace.
How do I connect Glen MCP to Zeplik?
You connect Glen MCP with a secure one-click sign-in (OAuth): press Connect in Settings under Connectors and approve access on Glen MCP's consent screen.
Does Zeplik change things in Glen MCP without asking?
No. Zeplik reads from Glen MCP by default. Any action that changes data in Glen MCP requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting Glen MCP cost?
Connecting Glen MCP is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related ai utilities integrations

More on Zeplik

Connect Glen MCP to your AI assistant

Every model, one chat. Bring Glen MCP into Zeplik and let the assistant do the work.