Docs · HTTP control

No MCP SDK required.

Any LLM or automation system that can make HTTPS requests can discover and call OMAS tools. The compact JSON bridge uses the same relay token, local approval, validation and audit path as the MCP endpoint.

Step 01

Keep the token URL secret

    
          $ export OMAS_URL=https://relay.omas.taps.im/t/<token>
        
          $ curl -sS "$OMAS_URL/http/tools"
        
          {"ok":true,"transport":"http","tools":[...]}

The token in the path is a bearer credential. Put it in a secret manager, never in a prompt, repository, analytics event or shared log. End or rotate the session if it is exposed.

Step 02

Call a tool with JSON

    
          $ curl -sS -X POST "$OMAS_URL/http/call" \
        
            -H 'content-type: application/json' \
        
            --data '{"tool":"repo_list_roots","arguments":{}}'
        
          {"ok":true,"tool":"repo_list_roots","response":{...}}

Request body

{
  "tool": "tool_name_from_http_tools",
  "arguments": { "repo_id": "approved-root" }
}

arguments defaults to an empty object. Unknown tools, malformed JSON and schema violations return a non-success HTTP status or an ok: false response with the normal structured tool result.

Local development

The same bridge on loopback

    
          $ curl -sS http://127.0.0.1:8787/http/tools
        
          $ curl -sS -X POST http://127.0.0.1:8787/http/call \
        
            -H 'content-type: application/json' \
        
            --data '{"tool":"repo_list_roots","arguments":{}}'

A token-scoped local server also accepts /t/<token>/http/toolsand /t/<token>/http/call. Bind OMAS to loopback unless a deliberate tunnel or reverse proxy provides the public boundary.

Security boundary

A shorter protocol, not a wider permission

Local approval still gates every call. A token cannot click Allow or press Enter.
Tool schemas still apply. Arguments and results follow the same bounded MCP tool implementation.
Audit events still fire. Calls record the tool, outcome and timing without recording values.
The relay still opens nothing inbound. The client keeps its outbound connection to the token relay.

Browse the tools Read the security model