{"version":"2.1.265","anchor":"artifact-shared-database-description-now-names-the-actual","canonical_anchor":"artifact-shared-database-description-now-names-the-actual","heading":"Artifact 'shared database' description now names the actual MCP servers built for the session","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/artifact-shared-database-description-now-names-the-actual","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Artifact 'shared database' description now names the actual MCP servers built for the session\n\nArtifact database help text now names the actual MCP servers built for the session instead of a generic description\n\n**What**\n\nThe \"Separate tools\" explanation shown for artifact database access now checks whether the `data` and `endpoints` MCP servers were actually built for the current session, and if so, names them individually instead of describing one generic artifact database tool. This includes a new description for server-run endpoints covering `get_endpoints`, `call_endpoint`, and `run_script`.\n\n**Why**\n\nThis makes the help text more accurate for a given session, telling the reader specifically which tools are available rather than a one-size-fits-all description that might not match what's actually set up.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}