Data Observability MCP Server
Overview
The Data Observability's Model Context Protocol (MCP) server enables seamless integration with AI assistants like Claude, allowing you to interact with your data quality platform directly through conversational interfaces. This integration provides access to Data Observability's comprehensive set of tools for monitoring, alerting, and data quality management.
What is MCP?
MCP is a standard that allows AI applications to securely connect to external services and data sources. Data Observability's MCP server exposes your data quality platform's capabilities as tools that can be invoked conversationally through compatible AI assistants.
Getting Started
Prerequisites
Before connecting to Data Observability's MCP server, ensure you have:
Access to Claude Desktop, Claude.ai, or a compatible MCP client (e.g., VSCode with Cline)
Valid Data Observability-Okta credentials
Specific MCP Server details:
OAuth client credentials (Client ID and Client Secret) for your application
MCP URL for your environment
Important:
You must be added to the associated application in Okta to complete OAuth authentication
MCP server URL and client credentials must be obtained from your Data Observability deployment owner
Connecting to Claude
Method 1: Claude Desktop or Claude.ai
Claude supports secure OAuth-based authentication, providing the most seamless integration experience.
Step 1: Access Connector Settings
Open your Claude Desktop application or visit
claude.aiClick your Profile Name or Avatar (usually located on the left sidebar or top corner)
Navigate to Settings
Look for the Connectors or Integrations section
Step 2: Add the Custom Connector
In the Connectors section, click Add custom connector
A configuration dialog will appear with the following fields:
Name: Enter a descriptive name (e.g., "Data Observability MCP")
URL: Enter your Data Observability MCP server URL (e.g., https://mcp.yourdomain.Data Observability.dev/yourorg/mcp)
Click Advanced Details to expand additional options
Enter your OAuth credentials:
Step 3: Initiate the OAuth Flow
Click Connect for the newly added server
Claude will recognize that OAuth authentication is required
Your default web browser will automatically open to the Data Observability-Okta login screen
Enter your Data Observability-Okta credentials and sign in
Review and approve the requested permissions
Step 4: Verify the Connection
After successful authorization, your browser will redirect back to Claude
Return to the Connectors section in Claude settings
Your Data Observability MCP server should now display as Connected with a green indicator
Step 5: Start Using Data Observability
Start a new chat in Claude
You can now ask questions about your data quality, create monitors, review alerts, and more
Claude will automatically use Data Observability's MCP tools when relevant to your queries
Example prompts to try:
"Show me my recent incidents"
"What assets are available in my production project?"
"Create a completeness monitor for my customer table"
"Get the profiling data for my sales dataset"
Connecting with VSCode Cline
Cline is a VSCode extension that supports MCP servers but requires bearer token authentication instead of OAuth.
Note: Bearer tokens expire after a set period (typically 1 hour). You'll need to regenerate and update the token when it expires.
Step 1: Generate Bearer Token
Run the following command in your terminal to generate an access token:
CLIENT_ID="<your_client_id>"
CLIENT_SECRET="<your_client_secret>"
TOKEN_RESPONSE=$(curl -s -X POST "https://<okta_server>/oauth2/default/v1/token" \
-u "${CLIENT_ID}:${CLIENT_SECRET}" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=client_credentials&scope=mcp:access")
echo $(echo "$TOKEN_RESPONSE" | jq -r '.access_token')
Prerequisites:
The command will output your bearer token. Copy this token for the next step.
Step 2: Configure MCP Server in Cline
Open VSCode with the Cline extension installed
Click the MCP server settings button in the Cline interface
Select Remote Servers
Click Add server details
Provide the following information:
Name: Data Observability (or any descriptive name)
URL: Your Data Observability MCP server URL (e.g., https://mcp.dev.telm.ai/yourorg/mcp)
Step 3: Add Authorization Header
Click Edit Configuration to open the MCP settings JSON file
Locate the server configuration you just added
Add a headers section with your bearer token:
{
"mcpServers": {
"Data Observability": {
"url": "https://mcp.yourexampledomain.com/commonstock/mcp",
"type": "streamableHttp",
"disabled": false,
"autoApprove": [],
"headers": {
"Authorization": "Bearer eyJraWQiOiJ..."
}
}
}
}
Note: Save the configuration file
Step 4: Start Using Data Observability in Cline
Start a new Cline conversation in VSCode
Cline can now access Data Observability's MCP tools
Try asking questions about your data quality or requesting specific operations
Example prompts:
"List all my data assets in Data Observability"
"Show me open incidents from the last week"
"What monitors are configured for my warehouse connection?"
Token Refresh
When your bearer token expires, you'll need to:
Generate a new token using the curl command from Step 1
Update the Authorization header in your Cline configuration
Restart Cline or reload the MCP server connection
Available Tools
Once connected, your AI assistant has access to the following Data Observability capabilities:
Security Considerations
OAuth Authentication (Recommended)
Uses industry-standard OAuth 2.0 protocol
Tokens are securely managed by Claude
Automatic token refresh
Immediate revocation through Okta admin console
Audit trail of access events
Bearer Token Authentication
Tokens expire after a set period (typically 1 hour)
Tokens should be treated as passwords—never commit them to version control
Regenerate tokens regularly
Revoke compromised tokens immediately through Okta
Best Practices
Never share your Client Secret or Bearer Tokens
Use separate OAuth applications for production and development environments
Regularly audit connected applications in your Okta dashboard
Revoke access for applications you no longer use
Troubleshooting
OAuth Connection Issues
Bearer Token Issues
General Issues
Last modified date: 02/20/2026