dsigns guides · Connect accounts

Connect Claude or Codex

Manage sites, screens and content through MCP.

Codex setup

codex mcp add dsigns --url https://dsigns.bitprecision.com/api/mcp
codex mcp login dsigns

After signing in, ask: “Check my dsigns connection and list my players.”

Choose your connection
Add https://dsigns.bitprecision.com/api/mcp to your AI client. Use OAuth where supported: sign in to dsigns, choose the customer and review the requested permissions.
Use a key when your client needs one
Open Settings → Integrations → MCP & API to create a named, expiring API key. Store it in your client’s credential store, never in a prompt or shared file. Customer connections cover all sites in that customer; master access is restricted to platform administrators.
Start with a read, then prepare your changes
Ask the client to call get_connection and list_players. Use get_management_guide for complete operating instructions, including site setup, slides and layouts, uploads, publication, diagnostics and supported player controls.
Preview, publish and check the result
Ask your client to call preview_publication, review the affected screens, then use publish_player for the authorised changes. Ask for player status until the applied revision matches. Check the physical display to confirm its picture. The dashboard publishing control is shown below for reference; the MCP tools use the same publication checks.
Actual app controlsDashboard reference: MCP publication uses the same shared publication checks.