strava-activity-mcp-server 0.2.3__tar.gz → 0.2.4__tar.gz

{strava_activity_mcp_server-0.2.3 → strava_activity_mcp_server-0.2.4}/.python-version

@@ -1 +1 @@
-3.13
+3.13

{strava_activity_mcp_server-0.2.3 → strava_activity_mcp_server-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: strava-activity-mcp-server
-Version: 0.2.3
+Version: 0.2.4
 Summary: Strava MCP server: one-time browser auth, then automatic refresh-token login
 License-File: LICENSE
 Requires-Python: >=3.10

{strava_activity_mcp_server-0.2.3 → strava_activity_mcp_server-0.2.4}/pyproject.toml

@@ -1,21 +1,21 @@
-[project]
-name = "strava-activity-mcp-server"
-version = "0.2.3"
-description = "Strava MCP server: one-time browser auth, then automatic refresh-token login"
-readme = "README.md"
-requires-python = ">=3.10"
-dependencies = [
-    "build>=1.3.0",
-    "mcp[cli]>=1.16.0",
-    "twine>=6.2.0",
-]
-
-[project.scripts]
-strava-activity-mcp-server = "strava_activity_mcp_server:main"
-
-[build-system]
-requires = ["hatchling"]
-build-backend = "hatchling.build"
-
-[tool.hatch.build.targets.wheel]
-packages = ["src/strava_activity_mcp_server"]
+[project]
+name = "strava-activity-mcp-server"
+version = "0.2.4"
+description = "Strava MCP server: one-time browser auth, then automatic refresh-token login"
+readme = "README.md"
+requires-python = ">=3.10"
+dependencies = [
+    "build>=1.3.0",
+    "mcp[cli]>=1.16.0",
+    "twine>=6.2.0",
+]
+
+[project.scripts]
+strava-activity-mcp-server = "strava_activity_mcp_server:main"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/strava_activity_mcp_server"]

{strava_activity_mcp_server-0.2.3 → strava_activity_mcp_server-0.2.4}/ref/prompts.md

@@ -1,231 +1,231 @@
-Title: Prompts - Model Context Protocol
-
-URL Source: http://modelcontextprotocol.io/specification/2025-06-18/server/prompts
-
-Markdown Content:
-The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt templates to clients. Prompts allow servers to provide structured messages and instructions for interacting with language models. Clients can discover available prompts, retrieve their contents, and provide arguments to customize them.
-
-User Interaction Model
-----------------------
-
-Prompts are designed to be **user-controlled**, meaning they are exposed from servers to clients with the intention of the user being able to explicitly select them for use.Typically, prompts would be triggered through user-initiated commands in the user interface, which allows users to naturally discover and invoke available prompts.For example, as slash commands:![Image 1: Example of prompt exposed as slash command](https://mintcdn.com/mcp/4ZXF1PrDkEaJvXpn/specification/2025-06-18/server/slash-command.png?fit=max&auto=format&n=4ZXF1PrDkEaJvXpn&q=85&s=7f003e36d881dd6f3e5b8cbdd85e5ca5)However, implementors are free to expose prompts through any interface pattern that suits their needs—the protocol itself does not mandate any specific user interaction model.
-
-Capabilities
-------------
-
-Servers that support prompts **MUST** declare the `prompts` capability during [initialization](https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle#initialization):
-
-```
-{
-  "capabilities": {
-    "prompts": {
-      "listChanged": true
-    }
-  }
-}
-```
-
-`listChanged` indicates whether the server will emit notifications when the list of available prompts changes.
-
-Protocol Messages
------------------
-
-### Listing Prompts
-
-To retrieve available prompts, clients send a `prompts/list` request. This operation supports [pagination](https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/pagination).**Request:**
-
-```
-{
-  "jsonrpc": "2.0",
-  "id": 1,
-  "method": "prompts/list",
-  "params": {
-    "cursor": "optional-cursor-value"
-  }
-}
-```
-
-**Response:**
-
-```
-{
-  "jsonrpc": "2.0",
-  "id": 1,
-  "result": {
-    "prompts": [
-      {
-        "name": "code_review",
-        "title": "Request Code Review",
-        "description": "Asks the LLM to analyze code quality and suggest improvements",
-        "arguments": [
-          {
-            "name": "code",
-            "description": "The code to review",
-            "required": true
-          }
-        ]
-      }
-    ],
-    "nextCursor": "next-page-cursor"
-  }
-}
-```
-
-### Getting a Prompt
-
-To retrieve a specific prompt, clients send a `prompts/get` request. Arguments may be auto-completed through [the completion API](https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/completion).**Request:**
-
-```
-{
-  "jsonrpc": "2.0",
-  "id": 2,
-  "method": "prompts/get",
-  "params": {
-    "name": "code_review",
-    "arguments": {
-      "code": "def hello():\n    print('world')"
-    }
-  }
-}
-```
-
-**Response:**
-
-```
-{
-  "jsonrpc": "2.0",
-  "id": 2,
-  "result": {
-    "description": "Code review prompt",
-    "messages": [
-      {
-        "role": "user",
-        "content": {
-          "type": "text",
-          "text": "Please review this Python code:\ndef hello():\n    print('world')"
-        }
-      }
-    ]
-  }
-}
-```
-
-### List Changed Notification
-
-When the list of available prompts changes, servers that declared the `listChanged` capability **SHOULD** send a notification:
-
-```
-{
-  "jsonrpc": "2.0",
-  "method": "notifications/prompts/list_changed"
-}
-```
-
-Message Flow
-------------
-
-Data Types
-----------
-
-### Prompt
-
-A prompt definition includes:
-
-*   `name`: Unique identifier for the prompt
-*   `title`: Optional human-readable name of the prompt for display purposes.
-*   `description`: Optional human-readable description
-*   `arguments`: Optional list of arguments for customization
-
-### PromptMessage
-
-Messages in a prompt can contain:
-
-*   `role`: Either “user” or “assistant” to indicate the speaker
-*   `content`: One of the following content types:
-
-#### Text Content
-
-Text content represents plain text messages:
-
-```
-{
-  "type": "text",
-  "text": "The text content of the message"
-}
-```
-
-This is the most common content type used for natural language interactions.
-
-#### Image Content
-
-Image content allows including visual information in messages:
-
-```
-{
-  "type": "image",
-  "data": "base64-encoded-image-data",
-  "mimeType": "image/png"
-}
-```
-
-The image data **MUST** be base64-encoded and include a valid MIME type. This enables multi-modal interactions where visual context is important.
-
-#### Audio Content
-
-Audio content allows including audio information in messages:
-
-```
-{
-  "type": "audio",
-  "data": "base64-encoded-audio-data",
-  "mimeType": "audio/wav"
-}
-```
-
-The audio data MUST be base64-encoded and include a valid MIME type. This enables multi-modal interactions where audio context is important.
-
-#### Embedded Resources
-
-Embedded resources allow referencing server-side resources directly in messages:
-
-```
-{
-  "type": "resource",
-  "resource": {
-    "uri": "resource://example",
-    "name": "example",
-    "title": "My Example Resource",
-    "mimeType": "text/plain",
-    "text": "Resource content"
-  }
-}
-```
-
-Resources can contain either text or binary (blob) data and **MUST** include:
-
-*   A valid resource URI
-*   The appropriate MIME type
-*   Either text content or base64-encoded blob data
-
-Embedded resources enable prompts to seamlessly incorporate server-managed content like documentation, code samples, or other reference materials directly into the conversation flow.
-
-Error Handling
---------------
-
-Servers **SHOULD** return standard JSON-RPC errors for common failure cases:
-
-*   Invalid prompt name: `-32602` (Invalid params)
-*   Missing required arguments: `-32602` (Invalid params)
-*   Internal errors: `-32603` (Internal error)
-
-Implementation Considerations
------------------------------
-
-1.   Servers **SHOULD** validate prompt arguments before processing
-2.   Clients **SHOULD** handle pagination for large prompt lists
-3.   Both parties **SHOULD** respect capability negotiation
-
-Security
---------
-
-Implementations **MUST** carefully validate all prompt inputs and outputs to prevent injection attacks or unauthorized access to resources.
+Title: Prompts - Model Context Protocol
+
+URL Source: http://modelcontextprotocol.io/specification/2025-06-18/server/prompts
+
+Markdown Content:
+The Model Context Protocol (MCP) provides a standardized way for servers to expose prompt templates to clients. Prompts allow servers to provide structured messages and instructions for interacting with language models. Clients can discover available prompts, retrieve their contents, and provide arguments to customize them.
+
+User Interaction Model
+----------------------
+
+Prompts are designed to be **user-controlled**, meaning they are exposed from servers to clients with the intention of the user being able to explicitly select them for use.Typically, prompts would be triggered through user-initiated commands in the user interface, which allows users to naturally discover and invoke available prompts.For example, as slash commands:![Image 1: Example of prompt exposed as slash command](https://mintcdn.com/mcp/4ZXF1PrDkEaJvXpn/specification/2025-06-18/server/slash-command.png?fit=max&auto=format&n=4ZXF1PrDkEaJvXpn&q=85&s=7f003e36d881dd6f3e5b8cbdd85e5ca5)However, implementors are free to expose prompts through any interface pattern that suits their needs—the protocol itself does not mandate any specific user interaction model.
+
+Capabilities
+------------
+
+Servers that support prompts **MUST** declare the `prompts` capability during [initialization](https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle#initialization):
+
+```
+{
+  "capabilities": {
+    "prompts": {
+      "listChanged": true
+    }
+  }
+}
+```
+
+`listChanged` indicates whether the server will emit notifications when the list of available prompts changes.
+
+Protocol Messages
+-----------------
+
+### Listing Prompts
+
+To retrieve available prompts, clients send a `prompts/list` request. This operation supports [pagination](https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/pagination).**Request:**
+
+```
+{
+  "jsonrpc": "2.0",
+  "id": 1,
+  "method": "prompts/list",
+  "params": {
+    "cursor": "optional-cursor-value"
+  }
+}
+```
+
+**Response:**
+
+```
+{
+  "jsonrpc": "2.0",
+  "id": 1,
+  "result": {
+    "prompts": [
+      {
+        "name": "code_review",
+        "title": "Request Code Review",
+        "description": "Asks the LLM to analyze code quality and suggest improvements",
+        "arguments": [
+          {
+            "name": "code",
+            "description": "The code to review",
+            "required": true
+          }
+        ]
+      }
+    ],
+    "nextCursor": "next-page-cursor"
+  }
+}
+```
+
+### Getting a Prompt
+
+To retrieve a specific prompt, clients send a `prompts/get` request. Arguments may be auto-completed through [the completion API](https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/completion).**Request:**
+
+```
+{
+  "jsonrpc": "2.0",
+  "id": 2,
+  "method": "prompts/get",
+  "params": {
+    "name": "code_review",
+    "arguments": {
+      "code": "def hello():\n    print('world')"
+    }
+  }
+}
+```
+
+**Response:**
+
+```
+{
+  "jsonrpc": "2.0",
+  "id": 2,
+  "result": {
+    "description": "Code review prompt",
+    "messages": [
+      {
+        "role": "user",
+        "content": {
+          "type": "text",
+          "text": "Please review this Python code:\ndef hello():\n    print('world')"
+        }
+      }
+    ]
+  }
+}
+```
+
+### List Changed Notification
+
+When the list of available prompts changes, servers that declared the `listChanged` capability **SHOULD** send a notification:
+
+```
+{
+  "jsonrpc": "2.0",
+  "method": "notifications/prompts/list_changed"
+}
+```
+
+Message Flow
+------------
+
+Data Types
+----------
+
+### Prompt
+
+A prompt definition includes:
+
+*   `name`: Unique identifier for the prompt
+*   `title`: Optional human-readable name of the prompt for display purposes.
+*   `description`: Optional human-readable description
+*   `arguments`: Optional list of arguments for customization
+
+### PromptMessage
+
+Messages in a prompt can contain:
+
+*   `role`: Either “user” or “assistant” to indicate the speaker
+*   `content`: One of the following content types:
+
+#### Text Content
+
+Text content represents plain text messages:
+
+```
+{
+  "type": "text",
+  "text": "The text content of the message"
+}
+```
+
+This is the most common content type used for natural language interactions.
+
+#### Image Content
+
+Image content allows including visual information in messages:
+
+```
+{
+  "type": "image",
+  "data": "base64-encoded-image-data",
+  "mimeType": "image/png"
+}
+```
+
+The image data **MUST** be base64-encoded and include a valid MIME type. This enables multi-modal interactions where visual context is important.
+
+#### Audio Content
+
+Audio content allows including audio information in messages:
+
+```
+{
+  "type": "audio",
+  "data": "base64-encoded-audio-data",
+  "mimeType": "audio/wav"
+}
+```
+
+The audio data MUST be base64-encoded and include a valid MIME type. This enables multi-modal interactions where audio context is important.
+
+#### Embedded Resources
+
+Embedded resources allow referencing server-side resources directly in messages:
+
+```
+{
+  "type": "resource",
+  "resource": {
+    "uri": "resource://example",
+    "name": "example",
+    "title": "My Example Resource",
+    "mimeType": "text/plain",
+    "text": "Resource content"
+  }
+}
+```
+
+Resources can contain either text or binary (blob) data and **MUST** include:
+
+*   A valid resource URI
+*   The appropriate MIME type
+*   Either text content or base64-encoded blob data
+
+Embedded resources enable prompts to seamlessly incorporate server-managed content like documentation, code samples, or other reference materials directly into the conversation flow.
+
+Error Handling
+--------------
+
+Servers **SHOULD** return standard JSON-RPC errors for common failure cases:
+
+*   Invalid prompt name: `-32602` (Invalid params)
+*   Missing required arguments: `-32602` (Invalid params)
+*   Internal errors: `-32603` (Internal error)
+
+Implementation Considerations
+-----------------------------
+
+1.   Servers **SHOULD** validate prompt arguments before processing
+2.   Clients **SHOULD** handle pagination for large prompt lists
+3.   Both parties **SHOULD** respect capability negotiation
+
+Security
+--------
+
+Implementations **MUST** carefully validate all prompt inputs and outputs to prevent injection attacks or unauthorized access to resources.

{strava_activity_mcp_server-0.2.3 → strava_activity_mcp_server-0.2.4}/src/strava_activity_mcp_server/__init__.py

@@ -1,4 +1,4 @@
-from .strava_activity_mcp_server import mcp
-def main() -> None:
-    """Run the MCP server."""
+from .strava_activity_mcp_server import mcp
+def main() -> None:
+    """Run the MCP server."""
     mcp.run()

{strava_activity_mcp_server-0.2.3 → strava_activity_mcp_server-0.2.4}/src/strava_activity_mcp_server/strava_activity_mcp_server.py

@@ -196,8 +196,6 @@ async def get_athlete_stats(
         "save": save_result
     }
 
-    return response.json()
-
 @mcp.tool("strava://athlete/stats-with-token")
 async def get_athlete_stats_with_token(access_token: str) -> dict:
     """Get athlete activities using an existing access token."""
@@ -219,7 +217,12 @@ async def get_athlete_stats_with_token(access_token: str) -> dict:
     except Exception as e:
         return {"error": "API request failed", "status_code": response.status_code, "response": response.text, "error": str(e)}
 
-    return response.json()
+    activities_data = response.json()
+    return {
+        "activities": activities_data,
+        "count": len(activities_data) if isinstance(activities_data, list) else 0,
+        "status": "success"
+    }
 
 @mcp.tool("strava://auth/save")
 async def save_tokens(tokens: dict | None = None) -> dict:

{strava_activity_mcp_server-0.2.3 → strava_activity_mcp_server-0.2.4}/uv.lock

@@ -1,5 +1,5 @@
 version = 1
-revision = 3
+revision = 2
 requires-python = ">=3.10"
 
 [[package]]
@@ -1031,7 +1031,7 @@ wheels = [
 
 [[package]]
 name = "strava-activity-mcp-server"
-version = "0.2.3"
+version = "0.2.4"
 source = { editable = "." }
 dependencies = [
     { name = "build" },