accessibility_simulate — Colour Memory MCP Tool
accessibility_simulate
(accessibility simulate) is one of 91 tools on the
Colour Memory
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call accessibility_simulate from your client
- Claude Code Colour Memory accessibility_simulate run in your project directory
- Claude Desktop Colour Memory accessibility_simulate ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Colour Memory accessibility_simulate ~/.cursor/mcp.json
- VS Code Colour Memory accessibility_simulate .vscode/mcp.json
- Zed Colour Memory accessibility_simulate ~/.config/zed/settings.json
- Windsurf Colour Memory accessibility_simulate ~/.codeium/windsurf/mcp_config.json
- Cline Colour Memory accessibility_simulate ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Colour Memory accessibility_simulate ~/.gemini/settings.json
- Grok Colour Memory accessibility_simulate .mcp.json (in your project root)
- ChatGPT Colour Memory accessibility_simulate Settings → Connectors → Advanced → Developer mode
- Claude.ai Colour Memory accessibility_simulate Settings → Connectors → Add custom connector
- LangChain Colour Memory accessibility_simulate pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http colour-memory https://colour-memory-api-production.up.railway.app/mcpOther tools on this server
- query_conceptual
- extract_image_colours
- query_hex
- palette_specify
- colour_metrics
- colour_harmonies
- accessibility_check
- accessibility_matrix
- accessibility_rules
- colour_slugs
- palette_light_dark
- accessibility_font
- archive_search
- colour_combination
- palette_strict
- palette_pdf
- palette_audit
- brand_system
- brand_asset_pack
- colour_match_paint
- colour_card
- meta_capabilities
- system_status
- colour_story
- palette_concept
- colour_mix
- colour_timeline
- image_palette
- colour_compare
- colour_cultural_risk
- design_session
- image_personal
- style_match
- interior_specify
- house_specify
- palette_generate
- palette_gradient
- palette_translate
- archive_cliche
- colour_verdict
- palette_verdict
- agent_brief
- colour_strategy
- archive_report_brief
- palette_heritage
- archive_coverage_gap
- archive_cultural_anachronism
- session_brief
- index_resonance
- archive_evidence_gap
- brand_collision
- brand_report
- brand_audit
- agent_verify
- colour_passport
- colour_passports
- colour_dna
- ecommerce_copy
- colour_hooks
- archive_provenance
- colour_forensics
- palette_iterate
- colour_variants
- palette_export
- palette_compare
- ecommerce_namer
- ui_states
- colour_namer
- palette_swatch
- palette_analyse
- ingest_image
- palette_extract
- image_brief
- project_get
- project_list
- project_versions
- project_delete
- project_export
- brand_guideline_specify
- brand_guideline_status
- brand_guideline_select
- brand_guideline_pdf
- brand_guideline_claims
- render_colour_result
- palette_finalize
- tool_guide
- historical_colour_query
- colour_relationships
- why_connected
- vanderpoel_pairing
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.