`GET` returns server metadata and tool descriptions. `POST` accepts MCP JSON-RPC methods including `initialize`, `ping`, `tools/list`, and `tools/call`.
MCP Server Docs
ArtiShare remote MCP server
ArtiShare exposes a remote MCP-compatible endpoint so Claude or any MCP-capable AI client can publish artifacts, manage recipient groups, and issue share links against the active workspace.
ArtiShare supports bearer-token access for remote connector use. When a valid Clerk session and active workspace are present, the app can also resolve the current user and organization context directly.
1. Authorization request
Clients can start an OAuth-style code flow with `/oauth/authorize`, using `response_type=code`, `redirect_uri`, and PKCE parameters.
2. Token exchange
Clients exchange the authorization code at `/oauth/token`. The server verifies the PKCE challenge before issuing a bearer token.
3. Protected resource metadata
The MCP endpoint advertises protected resource metadata and returns bearer challenges when unauthenticated requests reach protected methods.
publish_artifact
Publish a finished artifact snapshot into ArtiShare. If the artifact contains user-specific embedded data that should be reusable, use publish_templatized_artifact instead and replace those values with {{placeholder}} keys.
publish_templatized_artifact
Publish a reusable artifact template and its matching JSON data in one call. Before calling this tool, remove user-specific embedded data from the artifact content, replace it with {{placeholder_key}} tokens, and put the removed values into sampleData. The tool stores the placeholder contract as the template mapping JSON, enables the artifact as a template, and saves the inline JSON data source that can fill it.
update_artifact
Write a new immutable version for an existing ArtiShare artifact.
create_group
Create a reusable recipient group from email addresses.
update_group
Replace or rename an existing recipient group.
list_groups
List reusable recipient groups in the active organization.
create_share_link
Create a public or restricted share link for an artifact.
revoke_share_link
Revoke an existing share link.
set_share_expiration
Set or update an expiration date for a share link.
list_artifacts
List artifacts for the current organization.
list_artifact_shares
List share links for one artifact.
enable_artifact_template
Register an artifact as a reusable placeholder-driven template.
list_artifact_templates
List template-enabled artifacts in the active organization.
create_data_source_connection
Save an inline JSON data source for artifact template runs.
list_data_source_connections
List saved data source connections in the active organization.
run_artifact_template
Generate a new artifact by binding a saved data source to a template artifact.
list_artifact_runs
List template runs for one artifact.
publish_marketplace_listing
Publish an installable marketplace listing for an artifact.
list_marketplace_listings
List published marketplace artifacts.
install_marketplace_listing
Copy a marketplace artifact into the current workspace.
create_marketplace_review
Leave a rating and comment on a marketplace listing.
list_marketplace_reviews
List ratings and comments for a marketplace listing.
Publish and version artifacts
MCP-capable AI clients can publish a fresh artifact snapshot or write a new immutable version for an existing artifact.
Manage recipient groups
Admins can create and update reusable recipient groups made of named email recipients.
Create and manage share links
AI clients can issue public or restricted links, revoke links, set expirations, and inspect share state for an artifact.
Bind data into artifact templates
MCP clients can enable placeholder-driven templates, save inline JSON data sources, and generate derived artifacts by running a template against saved data.
Publish and install marketplace artifacts
MCP clients can publish installable marketplace listings, copy them into another workspace, and leave ratings and comments after teams start using them.
Respect workspace billing and roles
Connector calls are blocked until workspace setup and billing are complete, and admin-only operations remain restricted to admins.