What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://{openmetadata_host}/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Run this in your terminal

claude mcp add --transport http openmetadata 'https://{openmetadata_host}/mcp'

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "openmetadata": {
      "url": "https://{openmetadata_host}/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "openmetadata": {
      "type": "http",
      "url": "https://{openmetadata_host}/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://{openmetadata_host}/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account open-metadata, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
– Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7254 servers in this category
Published to the registry more recently than 40% of the other 7254 servers in this category
Basic checks equal to or better than 100% of the other 7254 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is OpenMetadata safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

OpenMetadata MCP OAuth Implementation

OAuth 2.0 authentication server for Model Context Protocol (MCP) integration with OpenMetadata, enabling secure access to metadata through Claude Desktop and other MCP clients.

Overview

This module implements a complete OAuth 2.0 Authorization Code Flow with PKCE for MCP clients, enabling user authentication via OpenMetadata's existing SSO providers (Google, Okta, Azure AD, Auth0, AWS Cognito, Custom OIDC, LDAP, SAML) or Basic Auth. The implementation provides secure, standards-compliant access to OpenMetadata's metadata management capabilities through MCP tools.

Important: This is user SSO authentication for MCP clients, not connector-based OAuth for data sources. Users authenticate with their OpenMetadata credentials (SSO or username/password), and MCP tools execute with that user's permissions.

Features

OAuth 2.0 Implementation

Authorization Code Flow with PKCE - RFC 7636 compliant, preventing authorization code interception attacks
Refresh Token Rotation - Automatic token refresh with rotation for enhanced security
Token Encryption - Fernet symmetric encryption for tokens at rest
CSRF Protection - State parameter validation across the OAuth flow
Session Fixation Prevention - Session regeneration after successful authentication

Authentication Methods

SSO Integration - OAuth 2.0 integration with Google, Okta, Azure AD, Auth0, AWS Cognito, Custom OIDC, LDAP, and SAML providers via pac4j
Basic Auth - Username/password authentication with OpenMetadata credentials
User Impersonation - Support for impersonated user contexts in MCP tools
Auto-Detection - Automatically selects SSO or Basic Auth based on OpenMetadata configuration

Security Features

PKCE Validation - SHA-256 code challenge/verifier validation
Token Expiry Management - Access tokens last 10 minutes; refresh tokens last 30 days from sign-in, and rotating them does not extend that
Rate Limiting - Registration (10/hour per IP) and token (30/minute per IP) endpoint protection
Thread-Safe Concurrent Processing - ThreadLocal storage for request isolation
Audit Logging - OAuth operations logged via SLF4J (oauth_audit_log table available for future use)
Read-only Mode - Turn on Read-only Mode in the MCP Server app settings to expose only tools annotated readOnlyHint, for every user including admins. Writes are blocked at once; the tool list changes, and turning it off applies, after a restart. Through the API, send the full configuration: PUT /api/v1/system/mcp/config replaces every field.
Disabled Tools - Pick tools under Disabled Tools in the MCP Server app settings to turn them off for every user including admins. Calls are refused at once; the tool list changes, and enabling a tool again applies, after a restart. GET /api/v1/system/mcp/tools lists the tool names the server registered.

Database-Driven Configuration

Runtime Configuration - Update MCP settings without server restart via REST API
Cluster Synchronization - Database polling (10-second interval) ensures all cluster instances have consistent configuration
Configuration Change Listeners - Dynamic CORS origin updates when configuration changes
Persistent Storage - Configuration changes persist across server restarts (database-first, YAML fallback)
HTTP Timeout Configuration - Configurable connection and read timeouts for SSO provider metadata fetching

MCP Integration

Claude Desktop Support - First-class integration with Claude Desktop MCP client
OAuth Discovery Endpoints - Standard .well-known endpoints for client configuration
Dynamic Client Registration - RFC 7591 compliant client registration
JWKS Support - Public key endpoint for JWT validation

Architecture

Core Components

UserSSOOAuthProvider

Main OAuth provider implementing authorization code flow
Handles both Google SSO and Basic Auth flows
Token generation, validation, and refresh logic
PKCE challenge/verifier validation with timing-safe comparison

OAuthHttpStatelessServerTransportProvider

HTTP transport layer for OAuth endpoints
Routes authorization, token, and discovery requests
Servlet-based stateless request handling
Provider-aware OAuth scope configuration

SecurityConfigurationManager

Singleton manager for runtime security configuration (authentication, authorization, MCP settings)
Database-first configuration loading with YAML fallback
Configuration change listener pattern for reactive updates
Cluster-aware polling mechanism (10-second interval) to detect changes across instances
Rollback mechanism for failed configuration updates
Thread-safe synchronized getters for consistent configuration reads

OAuth Repositories

OAuthClientRepository - Client management and validation
OAuthAuthorizationCodeRepository - Authorization code CRUD operations
OAuthAccessTokenRepository - Access token lifecycle management
OAuthRefreshTokenRepository - Refresh token rotation and cleanup
McpPendingAuthRequestRepository - Database-backed OAuth state persistence
OAuthAuditLogRepository - Comprehensive audit trail

Database Schema

Five core OAuth tables with audit logging:

oauth_clients - Dynamically registered MCP clients via RFC 7591
oauth_authorization_codes - Short-lived codes (10 min TTL) with PKCE challenge
oauth_access_tokens - Not written today: access tokens are 10-minute JWTs returned to the client
oauth_refresh_tokens - Refresh tokens (30 days from sign-in) with automatic rotation that keeps that end
mcp_pending_auth_requests - OAuth state parameters for cross-domain redirects (10 min TTL)
oauth_audit_log - Comprehensive audit trail of all OAuth operations

Cleanup Job: OAuthTokenCleanupJob runs every 10 minutes to purge expired tokens and pending requests.

OAuth Flow

Authorization Code Flow with PKCE

┌─────────────┐                                                    ┌──────────────┐

│ Claude │ │ OpenMetadata │ │ Desktop │ │ MCP │ │ (MCP Client)│ │ Server │ └──────┬──────┘ └──────┬───────┘ │ │ │ 1. Generate PKCE code_verifier (random 43-128 chars) │ │ Calculate code_challenge = BASE64URL(SHA256(verifier)) │ │ │ │ 2. GET /api/v1/mcp/authorize │ │ ?client_id={registered_client_id} │ │ &redirect_uri=http://127.0.0.1:XXXXX/callback │ │ &code_challenge={challenge} │ │ &code_challenge_method=S256 │ │ &state={client_state} │ │─────────────────────────────────────────────────────────────────>│ │ │ │ 3. Store OAuth state in database: │ │ - client_id, redirect_uri │ │ - code_challenge, method │ │ - state, scopes, TTL (10 min) │ │ Generate authRequestId │ │ │ │ 4. 302 Redirect to Auth Page │ │ /api/v1/mcp/authorize?state=mcp:{authRequestId} │ │<─────────────────────────────────────────────────────────────────│ │ │ │ 5. User authenticates via: │ │ ┌──────────────────────────────────────┐ │ │ │ Option A: SSO Provider │ │ │ │ - Redirect to SSO provider: │ │ │ │ • Google OAuth │ │ │ │ • Okta │ │ │ │ • Azure AD │ │ │ │ • Auth0 │ │ │ │ • AWS Cognito │ │ │ │ • Custom OIDC │ │ │ │ • LDAP │ │ │ │ • SAML │ │ │ │ - User grants consent │ │ │ │ - SSO callback with ID token (pac4j)│ │ │ └──────────────────────────────────────┘ │ │ OR │ │ ┌─────────────────────────────┐ │ │ │ Option B: Basic Auth │ │ │ │ - Username/password form │ │ │ │ - Validate with │ │ │ │ OpenMetadata │ │ │ └─────────────────────────────┘ │ │ │ │ 6. Lookup OAuth state from DB using │ │ authRequestId from state parameter │ │ Generate authorization code │ │ Store code + code_challenge in DB │ │ │ │ 7. 302 Redirect with authorization code │ │ {redirect_uri}?code={auth_code}&state={client_state} │ │<─────────────────────────────────────────────────────────────────│ │ │ │ 8. POST /api/v1/mcp/token │ │ grant_type=authorization_code │ │ code={auth_code} │ │ code_verifier={verifier} │ │ client_id={registered_client_id} │ │ redirect_uri=http://127.0.0.1:XXXXX/callback │ │─────────────────────────────────────────────────────────────────>│ │ │ │ 9. PKCE Validation: │ │ Lookup code_challenge from DB │ │ Verify: BASE64URL(SHA256(verifier)) │ │ == code_challenge │ │ Delete authorization code (single-use)│ │ │ │ 10. 200 OK │ │ { │ │ "access_token": "eyJhbGc...", // JWT, 10 min TTL │ │ "refresh_token": "fernet_encrypted", // 30 days TTL │ │ "token_type": "Bearer", │ │ "expires_in": 600

Only the beginning is shown; read the rest in the repo

OpenMetadata

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

OpenMetadata MCP OAuth Implementation

Overview

Features

OAuth 2.0 Implementation

Authentication Methods

Security Features

Database-Driven Configuration

MCP Integration

Architecture

Core Components

Database Schema

OAuth Flow

Authorization Code Flow with PKCE