@@ -37,7 +37,7 @@ The SDK is consumed from the npm registry:
3737## Environment
3838
3939``` sh
40- export BISIBILITY_API_KEY=" bsp_live_ ..."
40+ export BISIBILITY_API_KEY=" bsb_pat_live_ ..."
4141export BISIBILITY_BASE_URL=" https://bisibility.com/api/v1"
4242export BISIBILITY_PROJECT_ID=" prj_..."
4343export BISIBILITY_MCP_READ_ONLY=" 1"
@@ -46,18 +46,18 @@ export BISIBILITY_MCP_TOOLSETS="projects,keywords,checks,rank-history"
4646
4747` BISIBILITY_BASE_URL ` is optional and defaults to ` https://bisibility.com/api/v1 ` . For self-hosted
4848installs, set it to your API v1 root, for example ` https://rank.example/api/v1 ` .
49- ` BISIBILITY_API_KEY ` accepts a project key (` bsk_live_ ...` ) or personal access
50- token (` bsp_live_ ...` ). Set optional ` BISIBILITY_PROJECT_ID ` as the default
49+ ` BISIBILITY_API_KEY ` accepts a project key (` bsb_key_live_ ...` ) or personal access
50+ token (` bsb_pat_live_ ...` ). Set optional ` BISIBILITY_PROJECT_ID ` as the default
5151` X-Bisibility-Project ` selector for project-implicit PAT tools; a tool's
5252optional ` project_id ` argument overrides it for that call. Every resource ID
5353accepted by the MCP server, including ` BISIBILITY_PROJECT_ID ` , must use public
54- ID v2 : a canonical lowercase prefix plus ` _ ` and a 24-character lowercase
54+ ID v3 : a canonical lowercase prefix plus ` _ ` and a 24-character lowercase
5555CUID2 suffix, for example ` prj_a1b2c3d4e5f6g7h8j9k0m2n3 ` . Raw database IDs,
5656legacy IDs, mixed-case IDs, and wrong resource prefixes are rejected. Location
5757selection uses the returned ` location_key ` , never a location ID.
5858
59- The SDK dependency and lockfile use the published registry package. Do not use
60- a local SDK link.
59+ The server consumes the public ID v3 contract from the published
60+ ` @bisibility/sdk ` package. Do not replace it with a local SDK link.
6161
6262` BISIBILITY_MCP_READ_ONLY ` accepts ` 1 ` , ` true ` , ` yes ` , or ` on ` , ignoring case. When enabled,
6363write tools are not registered and do not appear in ` tools/list ` .
@@ -73,7 +73,7 @@ control, not a way to improve tool selection.
7373
7474``` sh
7575npm run build
76- BISIBILITY_API_KEY=" bsk_live_ ..." node dist/stdio.js
76+ BISIBILITY_API_KEY=" bsb_key_live_ ..." node dist/stdio.js
7777```
7878
7979When installed as a package, the bin is:
@@ -93,7 +93,7 @@ Example MCP client configuration using the built local package:
9393 "command" : " node" ,
9494 "args" : [" /path/to/bisibility-mcp/dist/stdio.js" ],
9595 "env" : {
96- "BISIBILITY_API_KEY" : " bsk_live_ ..." ,
96+ "BISIBILITY_API_KEY" : " bsb_key_live_ ..." ,
9797 "BISIBILITY_BASE_URL" : " https://bisibility.com/api/v1"
9898 }
9999 }
@@ -109,7 +109,7 @@ Example using the package bin:
109109 "bisibility" : {
110110 "command" : " bisibility-mcp" ,
111111 "env" : {
112- "BISIBILITY_API_KEY" : " bsk_live_ ..." ,
112+ "BISIBILITY_API_KEY" : " bsb_key_live_ ..." ,
113113 "BISIBILITY_BASE_URL" : " https://bisibility.com/api/v1"
114114 }
115115 }
@@ -230,9 +230,9 @@ registered tool surface.
230230## Security
231231
232232The credential's scope is the primary authorization control, and the server accepts two kinds.
233- A project key (` bsk_live_ ...` ) belongs to exactly one project, which bounds the damage from a
233+ A project key (` bsb_key_live_ ...` ) belongs to exactly one project, which bounds the damage from a
234234leak and makes it a good fit for a single-project or machine setup. A personal access token
235- (` bsp_live_ ...` ) covers the projects you are a member of, so one token serves them all; its
235+ (` bsb_pat_live_ ...` ) covers the projects you are a member of, so one token serves them all; its
236236effective access in each project is the lower of the token's scope and your role there, meaning
237237a token never grants more than the person behind it. Use ` BISIBILITY_PROJECT_ID ` to set the
238238default project for a token that spans several, as described under Environment above.
0 commit comments