Used for configuration management, specifically for storing GitHub authentication credentials needed for the MCP server setup
Provides versioning capabilities for all user data operations, maintaining change history with metadata that preserves UOR coherence
Provides authentication, data storage, and version control capabilities, allowing users to store their UOR data in personal repositories and authenticate using GitHub credentials
Enables hosting of the MCP server without dedicated infrastructure, serving the MCP protocol endpoint via HTTPS with branch-specific deployments for version control
Used for package management and running the MCP server through commands like 'npm install' and 'npm start'
Leverages TypeScript for implementing type-safe UOR abstract classes, transform functions for observer frames, and maintaining the core MCP protocol layer
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Model Context Protocol (MCP) - UOR Implementationshow me all concepts in my personal namespace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Model Context Protocol (MCP) - UOR Implementation
š¤ Welcome, Autonomous Agents!
UOR believes in co-creation: humans craft meaning, machines extend it.
Start here ā Comprehensive Documentation
Need vectors? ā Embeddings for Vector Search
Issue? Ping us: contact@uor.foundation
Related MCP server: GitHub MCP Server
Overview
The Model Context Protocol (MCP) implementation for the Universal Object Reference (UOR) Framework provides a standardized way for LLMs to access and manipulate UOR data. This implementation uses GitHub for data storage and version control, enabling a decentralized approach to UOR data management.
Key Features
Trilateral Coherence: Ensures consistency between objects, their representations, and observer frames
Canonical Representation: Provides a unique, basis-independent representation for each object
Namespace Resolution: Allows cross-namespace queries and decentralized content management
GitHub Integration: Uses GitHub for storage, authentication, and version control
OpenAPI Specification: Offers a machine-readable API description for easy integration
Docker Support: Provides Docker configuration for easy deployment and execution
Quick Start
Docker Deployment
To run the MCP server using Docker:
Local Deployment
Installation
Development
Testing
Building
Architecture
This implementation follows the core UOR architecture, built around the trilateral coherence relationship between:
Objects: The entities being represented
Representations: Base-independent canonical forms of objects
Observer Frames: Perspectives from which objects are viewed
The MCP server inherits from the UOR abstract TypeScript class, ensuring that all UOR invariant properties are maintained while providing an interface compatible with the MCP specification.
GitHub Integration
Server Hosting
Hosted via GitHub Pages from
github.com/UOR-Foundation/mcpRequires no dedicated server infrastructure
Serves the MCP protocol endpoint via HTTPS
Uses branch-specific deployments for version control
User Data Management
Each user can authenticate with GitHub credentials
Upon authentication, creates/accesses a personal
github.com/<username>/uordbrepositoryAll user data is stored in their personal repository
Repository structure follows the UOR schema organization with directories for: concepts, resources, topics, and predicates
Data Operations
Read: Fetches data via GitHub's raw content API (
https://raw.githubusercontent.com/<username>/uordb/main/...)Write: Commits changes to the user's
uordbrepository using GitHub APIAll operations maintain the UOR base-independent canonical representation
Changes are versioned through Git commit history with metadata that maintains UOR coherence
Namespace Resolution
Each user's data exists in their own GitHub namespace (
<username>/uordb)Users can create resolver records in their namespace that point to other namespaces
Resolver records are stored in a standard format at
<username>/uordb/resolvers/The MCP client can traverse these resolver records to query across namespaces
Creates a decentralized network of UOR content across GitHub repositories
Circular references are detected and handled appropriately
Protocol Implementation
The MCP implementation supports the standard MCP protocol features:
Resources
Provides access to UOR objects through standardized resource URIs
Resources include concepts, topics, predicates, and other information resources
All resources maintain canonical, base-independent representation
Resource URIs follow the pattern:
uor://<namespace>/<type>/<id>Supports HTTP transports mapped to GitHub raw content URLs
Tools
Supports CRUD operations on UOR objects
Provides querying capabilities across namespaces
Enables relationship traversal using predicate connections
Implements standardized MCP tool interfaces for UOR operations
Tool calls are authenticated against GitHub credentials
Observer Frames
Maintains consistent representation across different observer frames
Supports transformation between frames while preserving essential information
Implements frame-specific views while maintaining the invariant representation
Frame transformations are implemented through TypeScript transform functions
UOR Core Features
This implementation provides access to the UOR core features:
Prime Decomposition
Objects are factorized into their irreducible components
Factorization is unique and observer-independent
Implemented using the UOR abstract class methods for decomposition
Decomposition is cached for performance but recalculated when objects change
Canonical Representation
Each object has a unique, basis-independent representation
Representations maintain coherence across transformations
JSON serialization maintains the canonical structure
Implements UOR schema validation on all representations
Trilateral Coherence
Consistency is maintained between object, representation, and observer
Coherence measures quantify representational integrity
Coherence is verified during all write operations
Leverages the UOR kernel invariants inherited from the abstract class
Data Types and Schema Support
Supports all standard JSON Schema data types
Extends schema support beyond schema.org to custom domain schemas
Multimedia content uses chunked representation for efficient storage
All schemas conform to the UOR base-independent representation
Large artifacts use the Artifact schema for chunked storage
Security and Privacy
Authentication is handled via GitHub's OAuth system
Users maintain full control over their personal repositories
Cross-namespace queries only access publicly available data or repositories where the user has explicit access
Rate limiting follows GitHub API limits
OAuth scopes are limited to the specific repositories needed
GitHub Pages Deployment
The easiest way to use the MCP server is through our GitHub Pages deployment:
Visit https://68113dd199a34737508b5211--uor-mcp.netlify.app/
Configure the application with your GitHub Client ID and Token Exchange Proxy
Authenticate with GitHub to access your UOR data
Start using the MCP protocol with your LLM applications
Creating Your Own Deployment
To deploy your own instance:
Fork this repository
Create a GitHub OAuth application in your GitHub Developer Settings
Set the Authorization Callback URL to
https://api.netlify.com/auth/done
Deploy to Netlify (see Netlify Deployment Guide below)
Access your deployment at your Netlify URL (e.g.,
https://your-site-name.netlify.app)
Authentication via Netlify OAuth proxy
This application uses Netlify's built-in OAuth proxy for secure GitHub authentication:
The OAuth callback URL must be set to
https://api.netlify.com/auth/donein your GitHub OAuth app settingsThe GitHub client ID and secret are stored as environment variables in Netlify
To rotate credentials, update both the GitHub OAuth app and the Netlify environment variables
Netlify Deployment
To deploy to Netlify:
Connect your GitHub repository to Netlify
Configure the build settings:
Build command:
npm run build && npm run build:clientPublish directory:
dist/public
Add the following environment variables in Netlify:
GITHUB_CLIENT_ID: Your GitHub OAuth app client IDGITHUB_CLIENT_SECRET: Your GitHub OAuth app client secret
Deploy your site
Alternatively, you can use URL parameters to configure your deployment:
Usage with LLM Applications
To use this MCP server with LLM applications:
Configure your LLM app to use the MCP endpoint:
https://68113dd199a34737508b5211--uor-mcp.netlify.app/mcpAuthenticate your users with GitHub
Access UOR objects using the standard MCP protocol methods:
initialize- Set up the connectiontools/list- List available UOR toolsresources/list- List available UOR resourcestools/call- Execute UOR operations
Repository Structure
Contributing
Please see CONTRIBUTING.md for guidelines on how to contribute to this project.
Implementation Details
The MCP implementation is built as a TypeScript application that inherits from the UOR abstract class. It provides a faithful implementation of the Model Context Protocol while leveraging the mathematical foundation of the UOR Framework.
The server uses the following key technologies:
TypeScript for type-safe implementation
GitHub API for storage and authentication
JSON Schema for validation
MCP protocol for client/server communication
Vite for optimized builds
All content is stored in its reversible, base-independent representation, ensuring information integrity regardless of how the data is accessed or viewed. This implementation maintains a clean separation between the UOR kernel (abstract class) and the MCP protocol layer, allowing for future protocol upgrades without affecting the core UOR functionality.
License
This project is licensed under the MIT License - see the LICENSE file for details.