Backdocket MCP Server
This is the Model Context Protocol (MCP) Server for Backdocket's legal case management system. MCP enables AI assistants to securely access and interact with Backdocket's data through standardized tools and protocols.
🔗 MCP Protocol Endpoint
http://ai.backdocket.com/mcp
Connect your MCP-compatible AI assistant to this endpoint
Server Information
Server Name:
WEBSERVER
Environment:
Production
Server URL:
http://ai.backdocket.com/mcp
Uptime:
0m 0s
Requests:
0
Last Updated:
2025-10-23 00:09:29
MCP Server Endpoints
🎯 Primary MCP Endpoint: /mcp
Main protocol endpoint for MCP clients (requires JWT authentication)
🔍 MCP Authorization Discovery (RFC 9728)
These endpoints enable MCP clients to discover authentication requirements and authorization servers.
Protected Resource Metadata (Root): /.well-known/oauth-protected-resource
Describes this MCP server and lists authorization servers that protect it
Protected Resource Metadata (Path-based): /.well-known/oauth-protected-resource/mcp
Path-based discovery for the /mcp endpoint (returns same metadata as root)
🔐 Authorization Server Metadata (Proxied)
These endpoints proxy to the authorization server for convenience (not required by MCP spec).
OpenID Configuration: /.well-known/openid-configuration
OpenID Connect Discovery metadata from the authorization server
OAuth Authorization Server: /.well-known/oauth-authorization-server
OAuth 2.0 Authorization Server metadata (RFC 8414)
🛠️ Available MCP Tools
- Firms: List and access firm information
- Claims: Search, retrieve, and manage legal claims
- Contacts: Search and access contact information
- Advanced Searches: Execute and manage saved searches
🔐 Authentication & Discovery Flow
- Unauthorized Request: Client attempts to access
/mcpwithout authentication - 401 Response: Server returns 401 with
WWW-Authenticateheader pointing to metadata - Metadata Discovery: Client fetches
/.well-known/oauth-protected-resource - Authorization Server Discovery: Client extracts authorization server URL from metadata
- OAuth Flow: Client initiates OAuth 2.1 / PKCE flow with authorization server
- Authenticated Access: Client uses access token to call
/mcpendpoints
📋 Standards Compliance: This server implements OAuth 2.1, RFC 9728 (Protected Resource Metadata), RFC 6750 (Bearer Token Usage), and the Model Context Protocol Authorization Specification.