mirror of
https://github.com/varunneal/spotify-mcp.git
synced 2026-04-26 13:15:50 +03:00
[GH-ISSUE #12] No tools in Cursor #1
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-mcp-varunneal#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @woodyhayday on GitHub (Mar 18, 2025).
Original GitHub issue: https://github.com/varunneal/spotify-mcp/issues/12
Getting this when I try to hack this into my Cursor, any ideas?
@varunneal commented on GitHub (Mar 18, 2025):
Not 100% sure. Have you configured the environment variables?
@marcelmarais commented on GitHub (Mar 19, 2025):
Same issue for me
@0GiS0 commented on GitHub (Mar 19, 2025):
I have the same issue in VS Code Insiders with GitHub Copilot 🥸
@connor4312 commented on GitHub (Mar 19, 2025):
This is probably because this MCP server does not say that it supports tools in its capabilities.
Notice in the tutorial it has an example of setting an object for tools in the capabilities https://modelcontextprotocol.io/docs/concepts/tools#implementing-tools but this MCP server does not have that:
I notice you grab the options dict, which contains capability data, before tools are registered, which I'm just guessing is the issue (never used their Python SDK)
github.com/varunneal/spotify-mcp@732b3e8f11/src/spotify_mcp/server.py (L33)@varunneal commented on GitHub (Mar 19, 2025):
Great catch @connor4312! I'll talk a look later this evening and try to fix it
@connor4312 commented on GitHub (Mar 19, 2025):
If you want you can use VS Code Insiders and the
MCP: Add Servercommand to validate it ;)@varunneal commented on GitHub (Mar 20, 2025):
Would anyone in this thread like to verify if my recent commit fixed this issue for them? 😄
@connor4312 commented on GitHub (Mar 20, 2025):
works for vscode
@0GiS0 commented on GitHub (Mar 24, 2025):
Yeah! It works now! Thank you so much both!!