Assay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_API_KEY | No | Your Anthropic API key for optional server-side synthesis. | |
| FIREBASE_API_KEY | No | Override Firebase Web API key (optional). Default: Assay service key. | |
| ASSAY_FIREBASE_TOKEN | Yes | Your Firebase ID token for authentication. Required. Also can be provided via command-line argument --token. | |
| ASSAY_FUNCTIONS_BASE_URL | No | Override Cloud Functions endpoint (optional). Default: https://us-east4-pdfsummaries.cloudfunctions.net |
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
- 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/cirruslycurious/assay-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server