Skip to main content
Glama
prismism-dev

Prismism MCP Server

by prismism-dev

Register Prismism Account

prismism_register

Create a Prismism account and generate an API key for accessing file upload and sharing capabilities through the MCP server. Save the key immediately as it cannot be retrieved again.

Instructions

Create a new Prismism account and get an API key. This is a one-time setup tool. The API key is returned once and cannot be retrieved again — save it to your MCP config immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesYour name
emailYesYour email address — use a real email you can access

Implementation Reference

  • The handler function for the prismism_register tool, which performs a POST request to register a user and returns an API key.
    async ({ name, email }) => {
      const result = await post<{
        apiKey?: string;
        user?: { id: string; name: string; email: string };
        docs?: string;
        agentSkills?: string;
      }>('/v1/auth/register', { name, email });
    
      if (!result.ok) {
        const hints = result._hints || [];
    
        // Special handling for existing accounts
        if (result.error?.code === 'EMAIL_EXISTS') {
          hints.push(
            'This email is already registered. Create a new API key at https://prismism.dev/settings/api-keys and add it to your MCP config.'
          );
        }
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ ok: false, error: result.error, _hints: hints }),
            },
          ],
          isError: true,
        };
      }
    
      const baseUrl = getBaseUrl();
      const configSnippet = result.data?.apiKey
        ? `\n\nAdd this to your MCP config:\n{\n  "mcpServers": {\n    "prismism": {\n      "command": "npx",\n      "args": ["@prismism/mcp-server"],\n      "env": {\n        "PRISMISM_API_KEY": "${result.data.apiKey}"\n      }\n    }\n  }\n}`
        : '';
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              ok: true,
              data: result.data,
              _hints: [
                `Save this API key now — it cannot be retrieved again.${configSnippet}`,
                result.data?.docs ? `API docs: ${result.data.docs}` : null,
                result.data?.agentSkills ? `Agent skills: ${result.data.agentSkills}` : null,
              ].filter(Boolean),
            }),
          },
        ],
      };
    }
  • Input schema for the prismism_register tool using Zod.
    inputSchema: {
      name: z.string().describe('Your name'),
      email: z.string().email().describe('Your email address — use a real email you can access'),
    },
  • Registration function for the prismism_register tool.
    export function registerRegisterTool(server: McpServer) {
      server.registerTool(
        'prismism_register',
        {
          title: 'Register Prismism Account',
          description:
            'Create a new Prismism account and get an API key. This is a one-time setup tool. The API key is returned once and cannot be retrieved again — save it to your MCP config immediately.',
          inputSchema: {
            name: z.string().describe('Your name'),
            email: z.string().email().describe('Your email address — use a real email you can access'),
          },
        },
        async ({ name, email }) => {
          const result = await post<{
            apiKey?: string;
            user?: { id: string; name: string; email: string };
            docs?: string;
            agentSkills?: string;
          }>('/v1/auth/register', { name, email });
    
          if (!result.ok) {
            const hints = result._hints || [];
    
            // Special handling for existing accounts
            if (result.error?.code === 'EMAIL_EXISTS') {
              hints.push(
                'This email is already registered. Create a new API key at https://prismism.dev/settings/api-keys and add it to your MCP config.'
              );
            }
    
            return {
              content: [
                {
                  type: 'text',
                  text: JSON.stringify({ ok: false, error: result.error, _hints: hints }),
                },
              ],
              isError: true,
            };
          }
    
          const baseUrl = getBaseUrl();
          const configSnippet = result.data?.apiKey
            ? `\n\nAdd this to your MCP config:\n{\n  "mcpServers": {\n    "prismism": {\n      "command": "npx",\n      "args": ["@prismism/mcp-server"],\n      "env": {\n        "PRISMISM_API_KEY": "${result.data.apiKey}"\n      }\n    }\n  }\n}`
            : '';
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify({
                  ok: true,
                  data: result.data,
                  _hints: [
                    `Save this API key now — it cannot be retrieved again.${configSnippet}`,
                    result.data?.docs ? `API docs: ${result.data.docs}` : null,
                    result.data?.agentSkills ? `Agent skills: ${result.data.agentSkills}` : null,
                  ].filter(Boolean),
                }),
              },
            ],
          };
        }
      );
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Excellently discloses irreversible behavior: 'API key is returned once and cannot be retrieved again'. Warns of data loss risk if not saved. Minor gap: doesn't specify behavior if email already registered or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with zero waste: 1) Purpose, 2) Usage classification, 3) Critical warning. Front-loaded with action and resource. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Compensates well for missing output schema by describing the return value (API key) and critical handling requirements. Given simple 2-parameter input with complete schema coverage, description adequately covers complexity. Minor gap on error conditions (duplicate email).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage ('Your name', 'Your email address — use a real email you can access'). Description adds no parameter-specific semantics, but with complete schema coverage, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'Create' + specific resource 'Prismism account' + outcome 'get an API key'. The 'one-time setup' framing distinguishes this initialization tool from sibling management tools like prismism_account, prismism_update, and prismism_delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'one-time setup tool' establishing when to use it. Provides critical handling instruction to 'save it to your MCP config immediately'. Minor deduction for not explicitly naming what to use if account already exists (likely prismism_account).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/prismism-dev/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server