Skip to main content
Glama

OLCP documentation

Product

The product specification is one specification in two files. Neither may be implemented from alone; their own section 0 mandates a fusion into a single IMPLEMENTATION_PLAN.md before the first product code, and card 017 executes that fusion.

  • plan.md - the foundational plan: identity, OAuth, privacy, evaluation, idempotency, Voice, the practice loop and the four core tools. Governs those areas on any conflict.

  • teaching-intelligence.md - the complementary Teaching Intelligence specification: lessons, knowledge atoms, the Curriculum Track Compiler, the Session Compiler, pedagogical RAG, editorial ingestion, CEFR classification and the Model Gateway. Governs those areas on any conflict.

  • context.md - company stage and risk tolerance: what this project cannot afford to break.

  • identity/README.md - identity design for the remote MCP server: WorkOS AuthKit as authorization server, OLCP as resource server, provider comparison, minors and GDPR, endpoints, EU data residency.

Related MCP server: Context Intelligence Layer

Operations

  • execution/s0-readiness.md - what runs today, what is blocked, and the human setup checklist that unblocks the identity spikes. Read before starting the first code card.

Operating contracts

Research

Primary-source reports, kept because the decisions they support are still live.

The proof of concept

poc/ in the repository root is a retained experiment, not a migration target. It accepts a learner_id and keeps state in JSON - both of which the product forbids. It is kept because its findings are what justified the product design, and it must not be extended.

F
license - not found
Not graded
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • Person-owned AI memory that learns, not just stores — portable context for any MCP client.

  • Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.

  • Persistent memory and cross-session learning for AI coding assistants (hosted remote MCP).

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/avivancos/open-english'

If you have feedback or need assistance with the MCP directory API, please join our Discord server