Skip to main content
Glama
OperantKit

operantkit-mcp

Official
by OperantKit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

operantkit-mcp

:jp: 日本語版 README

An MCP server (stdio) that lets an AI assistant design reinforcement schedules with OperantKit instead of hand-writing FR/VI generators. The schedule is written as one contingency-dsl expression; the server checks it, simulates it against virtual subjects, and translates between the expression and a Method section.

Tools

Tool

Input

Output

check_dsl

source

ok, canonical (normalized DSL), ast, warnings, error (type, message) — errors are returned as data

simulate

source, one of exit_reinforcers / exit_time (s), virtual_rate_hz (1.0), seed (0), reinforcer_duration (0.5), output_path

session_seconds, counts per event type, responses_per_operandum, reinforcers_per_operandum, response and reinforcement rates per minute, okl_path

dsl_to_method

source, style (jeab English / jaba Japanese)

subjects, apparatus, procedure, references, markdown

method_to_dsl

text (Method-section prose)

dsl, schedules (with confidence and source_text), params, unrecognized_fragments

summarize_okl

path (OKL v1 log)

session_name, dsl (from the header), clock_type, session_seconds, counts per event type, operanda (responses and reinforcers per operandum), phase_markers

analyze_okl

path, analyses (any of prps / irt / bouts / matching; default all), png_path

prps and prp_values, irt, bouts, matching, png_path (cumulative record), notes

All tools return structured content with a published output schema.

  • simulate runs on a virtual clock: a session of minutes finishes in well under a second. The same seed gives the same result. A concurrent schedule gets one independent Poisson responder per component. Seed VI/VR/VT values with @algorithm(seed=N) in the DSL.

  • method_to_dsl uses the rule-based extractor only. No LLM is called; read unrecognized_fragments and fill the gaps yourself.

  • analyze_okl pools inter-response times over operanda. matching needs responses on operanda 0 and 1 and gives a one-condition estimate (log b fixed at 0); fit several conditions for a real bias estimate. An analysis that cannot be computed is null and explained in notes.

Related MCP server: cron-mcp

Install

pip install operantkit-mcp

Python 3.11+.

Use with Claude Code

claude mcp add --transport stdio operantkit -- operantkit-mcp
claude mcp list    # operantkit: operantkit-mcp - ✔ Connected

Any MCP client that launches stdio servers works the same way: the command is operantkit-mcp (or python -m operantkit_mcp).

Example

check_dsl("Conc(VI 30s, VI 60s, COD=2s)")
  → canonical "Conc(VI30s, VI60s, COD=2s)"
dsl_to_method("Conc(VI30s, VI60s, COD=2s)")
  → procedure "Responses were reinforced under a concurrent VI 30-s VI 60-s schedule.
               A 2-s changeover delay was in effect."
simulate("FI30s", exit_reinforcers=5, seed=0)
  → reinforcers_per_operandum [5], session_seconds ≥ 150
simulate("Conc(VI30s, VI60s)", exit_reinforcers=20, output_path="conc.txt")
analyze_okl("conc.txt", analyses=["matching"], png_path="conc.png")
  → matching.responses, matching.reinforcers, matching.sensitivity; conc.png

Dependencies

mcp (2.x), contingency-dsl-py, contingency-py, contingency-dsl2procedure, contingency-procedure2dsl, experiment-core, session-runner, session-recorder, experiment-io, session-analyzer (brings matplotlib, numpy, scipy).

Development

python -m venv .venv
.venv/bin/python -m pip install -e ".[test]"
.venv/bin/python -m pytest

License

MIT

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers