메뉴
Configure or repair Prisme.ai MCP environment and token storage without exposing credentials in chat. Use when an environment is unknown, no token is registered, a stored token is rejected, or the user asks to configure MCP authentication.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/prismeai/prismeai-mcp --skill prisme-mcp-setup명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Build a brand-new Prisme.ai App+MCP connector for a third-party SaaS using the tenant-context model (no HMAC), an entity-grouped registry driven by a generated OpenAPI spec, multi-mode auth (API key / OAuth2 client-credentials / OAuth2 per-user PKCE / JWT service-account) resolved by buildAppAuth, a central platform OAuth client (token-service model — zero-config `oauthCentral` tenant mode + maintainer view in the config SPA), per-user OAuth tokens resolvable from cron, a model-B config SPA, and optionally a **MCP Knowledge Resources** surface so the connector can feed a knowledge base (Phase 9). Reproduces the validated `salesforce-next` build (+ `google-workspaces` central OAuth) for any service. Use when the user says "build an app+mcp for X", "créer une app+mcp pour X", "implémente un connecteur X". Everything needed is here + in `reference/`.
Create a Prisme.ai bootstrap workspace that provisions an Agent Factory agent, attaches Storage-backed file or URL sources, seeds Agent Evaluations cases, runs evaluation, and validates the setup through the supported product apps Agents, Storage, and Evaluation.
Create or update a Prisme.ai App+MCP consumer workspace with a reusable Claude Sonnet 4.6 Agent Factory agent already connected to the connector MCP and an Agent Evaluations suite of representative prompts, then run and repair the consumer or connector until the suite passes. Use when testing an App+MCP connector, creating its `*-consumer` workspace, consolidating connector coverage, or diagnosing failing connector E2E automations.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | prisme-mcp-setup |
| description | Configure or repair Prisme.ai MCP environment and token storage without exposing credentials in chat. Use when an environment is unknown, no token is registered, a stored token is rejected, or the user asks to configure MCP authentication. |
Use this procedure when a Prisme.ai MCP tool reports that an environment is unknown, no token is registered, or a stored token was rejected.
set-token CLI as the default setup path.Common mappings:
| Studio URL | API URL |
|---|---|
https://sandbox.prisme.ai | https://api.sandbox.prisme.ai/v2 |
https://staging.prisme.ai | https://api.staging.prisme.ai/v2 |
https://studio.prisme.ai | https://api.studio.prisme.ai/v2 |
For other deployments, derive the API URL from the user's Prisme.ai host or ask the user to confirm it.
Identify the target environment name from the failed request or user request.
Tell the user to create a token in the target studio at:
<studio-url>/settings/tokens
Tell the user to run the exact CLI command from the MCP error in their own terminal. Preserve it as one shell command; do not insert line breaks inside quoted paths. The CLI prompts for the token, the Prisme API and Studio URLs, and an optional NODE_EXTRA_CA_CERTS PEM path. Give https://api.sandbox.prisme.ai/v2 and https://sandbox.prisme.ai as examples.
For a known environment:
node "<plugin>/build/index.js" set-token <environment> --config-dir "<config-dir>"
For an unknown environment:
node "<plugin>/build/index.js" set-token <environment> --api-url <api-url> --config-dir "<config-dir>"
After the command succeeds, retry the original MCP tool call with the same explicit environment.
Only if the user explicitly wants to paste the token in chat, warn them first:
Using set_token means the token is sent through this conversation to the LLM provider. The CLI path keeps it local.
Then call set_token with environment, token, and apiUrl for a new environment. Include studioUrl and nodeExtraCaCerts when needed.