Semantic Code Search MCP Server
Officialby elastic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP mode (default: 3000). | 3000 |
| SCS_MCP_SERVER_URL | No | Public URL of the server. Required for OAuth and non-localhost deployments. | |
| ELASTICSEARCH_INDEX | No | The name of the Elasticsearch index to use. | semantic-code-search |
| SCS_MCP_OAUTH_ISSUER | No | OIDC issuer URL. Required when SCS_MCP_OAUTH_ENABLED=true. | |
| ELASTICSEARCH_API_KEY | No | An API key for Elasticsearch authentication. | |
| SCS_MCP_OAUTH_ENABLED | No | Enable OAuth 2.0 bearer token authentication (HTTP mode only). | false |
| ELASTICSEARCH_CLOUD_ID | No | The Cloud ID for your Elastic Cloud instance. | |
| ELASTICSEARCH_ENDPOINT | No | The Elasticsearch endpoint URL (e.g., http://localhost:9200). Alternative to ELASTICSEARCH_CLOUD_ID and ELASTICSEARCH_API_KEY. | |
| SCS_MCP_OAUTH_AUDIENCE | No | Expected aud claim override. Use for Okta non-URL audiences (e.g., api://default). | |
| SCS_MCP_OAUTH_CLIENT_ID | No | Client ID for token introspection (opt-in). Requires SCS_MCP_OAUTH_CLIENT_SECRET. | |
| SCS_MCP_OAUTH_CLIENT_SECRET | No | Client secret for token introspection (opt-in). | |
| SCS_MCP_OAUTH_REQUIRED_SCOPES | No | Space-separated scopes the server requires on every token. Minimum openid for Okta. | |
| SCS_MCP_OAUTH_ALLOWED_CLIENT_IDS | No | Space-separated allowlist of OAuth client IDs. Empty = any client from the issuer. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/elastic/semantic-code-search-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server