Schema | Opus MCP Server

Opus MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`OPUS_SERVICE_KEY`	Yes	Your Opus service key for authentication. Get this from Opus platform: My Organization → gear icon → API Keys → Generate API Key

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.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
get_workflow_detailsB	Get workflow details including jobPayloadSchema that defines required inputs for a workflow
initiate_jobC	Initiate a new job for a workflow. Returns jobExecutionId required for subsequent operations
generate_file_upload_urlA	Generate presigned URL for file upload. Returns presignedUrl (for uploading) and fileUrl (to reference in job execution)
execute_jobB	Execute a job with populated input values. Use jobPayloadSchema from get_workflow_details to structure inputs correctly
get_job_statusC	Get the current status of a job execution (e.g., IN PROGRESS, COMPLETED, FAILED)
get_job_resultsA	Get the results of a completed job execution. Only works when job status is COMPLETED
get_job_audit_logB	Get detailed audit log of all system actions during job execution

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Moenamatics/Opus-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server