Skip to main content
Glama
hrishi0102

Spotify MCP Server

by hrishi0102

set-spotify-credentials

Configure Spotify authentication credentials (Client ID, Client Secret, Access Token, Refresh Token) for the Spotify MCP Server to enable user account interactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessTokenYesThe Spotify Access Token
clientIdYesThe Spotify Client ID
clientSecretYesThe Spotify Client Secret
refreshTokenYesThe Spotify Refresh Token

Implementation Reference

  • Core handler implementation for the set-spotify-credentials tool in the stdio MCP server. Stores credentials in spotifyAuthInfo object and returns success response.
    server.tool(
      "set-spotify-credentials",
      {
        clientId: z.string().describe("The Spotify Client ID"),
        clientSecret: z.string().describe("The Spotify Client Secret"),
        accessToken: z.string().describe("The Spotify Access Token"),
        refreshToken: z.string().describe("The Spotify Refresh Token"),
      },
      async ({ clientId, clientSecret, accessToken, refreshToken }) => {
        spotifyAuthInfo.clientId = clientId;
        spotifyAuthInfo.clientSecret = clientSecret;
        spotifyAuthInfo.accessToken = accessToken;
        spotifyAuthInfo.refreshToken = refreshToken;
    
        return {
          content: [
            {
              type: "text",
              text: "Spotify credentials set successfully. You can now use other Spotify tools.",
            },
          ],
        };
      }
    );
  • Handler implementation for set-spotify-credentials in stateless HTTP MCP server. Stores credentials in globalSpotifyAuthInfo.
    server.tool(
      "set-spotify-credentials",
      {
        clientId: z.string().describe("The Spotify Client ID"),
        clientSecret: z.string().describe("The Spotify Client Secret"),
        accessToken: z.string().describe("The Spotify Access Token"),
        refreshToken: z.string().describe("The Spotify Refresh Token"),
      },
      async ({ clientId, clientSecret, accessToken, refreshToken }) => {
        globalSpotifyAuthInfo.clientId = clientId;
        globalSpotifyAuthInfo.clientSecret = clientSecret;
        globalSpotifyAuthInfo.accessToken = accessToken;
        globalSpotifyAuthInfo.refreshToken = refreshToken;
    
        return {
          content: [
            {
              type: "text",
              text: "Spotify credentials set successfully. You can now use other Spotify tools.",
            },
          ],
        };
      }
  • Handler for set-spotify-credentials in SSE MCP server variant. Identical logic storing in spotifyAuthInfo.
    server.tool(
      "set-spotify-credentials",
      {
        clientId: z.string().describe("The Spotify Client ID"),
        clientSecret: z.string().describe("The Spotify Client Secret"),
        accessToken: z.string().describe("The Spotify Access Token"),
        refreshToken: z.string().describe("The Spotify Refresh Token"),
      },
      async ({ clientId, clientSecret, accessToken, refreshToken }) => {
        spotifyAuthInfo.clientId = clientId;
        spotifyAuthInfo.clientSecret = clientSecret;
        spotifyAuthInfo.accessToken = accessToken;
        spotifyAuthInfo.refreshToken = refreshToken;
    
        return {
          content: [
            {
              type: "text",
              text: "Spotify credentials set successfully. You can now use other Spotify tools.",
            },
          ],
        };
      }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/hrishi0102/spotify-mcp'

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