mcp-use 1.3.1__tar.gz → 1.3.3__tar.gz

mcp_use-1.3.3/.env.example

@@ -0,0 +1,61 @@
+# =============================================================================
+# MCP-Use Environment Configuration
+# =============================================================================
+# Copy this file to .env and fill in your actual values
+# The .env file is already in .gitignore and won't be committed
+
+# =============================================================================
+# Observability - Optional but recommended for debugging and monitoring
+# =============================================================================
+
+# Langfuse Configuration (https://langfuse.com)
+# Sign up at https://cloud.langfuse.com or self-host
+LANGFUSE_PUBLIC_KEY=pk-lf-your-public-key-here
+LANGFUSE_SECRET_KEY=sk-lf-your-secret-key-here
+# LANGFUSE_HOST=https://cloud.langfuse.com  # Default, uncomment for self-hosted
+
+# Laminar Configuration (https://www.lmnr.ai)
+# Sign up at https://www.lmnr.ai and get your project API key
+LAMINAR_PROJECT_API_KEY=your-laminar-project-api-key-here
+
+# =============================================================================
+# LLM Provider API Keys
+# =============================================================================
+
+# OpenAI
+OPENAI_API_KEY=sk-your-openai-api-key-here
+
+# Anthropic
+ANTHROPIC_API_KEY=sk-ant-your-anthropic-api-key-here
+
+# Google (for Gemini)
+GOOGLE_API_KEY=your-google-api-key-here
+
+# Azure OpenAI
+AZURE_OPENAI_API_KEY=your-azure-openai-key-here
+AZURE_OPENAI_ENDPOINT=https://your-resource-name.openai.azure.com/
+
+# =============================================================================
+# Debug and Development
+# =============================================================================
+
+# MCP-Use Debug Level (1=INFO, 2=DEBUG)
+DEBUG=1
+# Alternative debug variable
+MCP_USE_DEBUG=1
+
+# Disable specific features (set to 'false' to disable)
+# MCP_USE_LANGFUSE=false
+# MCP_USE_LAMINAR=false
+# MCP_USE_TELEMETRY=false
+
+# =============================================================================
+# MCP Server Specific Configuration
+# =============================================================================
+
+# E2B Sandbox (for sandboxed execution)
+E2B_API_KEY=your-e2b-api-key-here
+
+# Custom MCP server endpoints (if using HTTP/WebSocket servers)
+# MCP_SERVER_URL=http://localhost:8080
+# MCP_WEBSOCKET_URL=ws://localhost:8081

mcp_use-1.3.3/.github/release-drafter.yml

@@ -0,0 +1,32 @@
+name-template: 'v$RESOLVED_VERSION 🌈'
+tag-template: 'v$RESOLVED_VERSION'
+categories:
+  - title: '🚀 Features'
+    labels:
+      - 'feature'
+      - 'feat'
+      - 'enhancement'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'fix'
+      - 'bugfix'
+      - 'bug'
+  - title: '🧰 Maintenance'
+    label: 'chore'
+change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+change-title-escapes: '\<*_&' # You can add # and @ to disable mentions, and add ` to disable code blocks.
+version-resolver:
+  major:
+    labels:
+      - 'major'
+  minor:
+    labels:
+      - 'minor'
+  patch:
+    labels:
+      - 'patch'
+  default: patch
+template: |
+  ## Changes
+
+  $CHANGES

mcp_use-1.3.3/.github/workflows/changelog.yml

@@ -0,0 +1,74 @@
+name: "Update Changelogs"
+
+on:
+  release:
+    types: [released]
+
+jobs:
+  update:
+    runs-on: ubuntu-latest
+
+    permissions:
+      # Give the default GITHUB_TOKEN write permission to commit and push the
+      # updated CHANGELOG back to the repository.
+      # https://github.blog/changelog/2023-02-02-github-actions-updating-the-default-github_token-permissions-to-read-only/
+      contents: write
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.release.target_commitish }}
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Update Changelog
+        uses: stefanzweifel/changelog-updater-action@v1
+        with:
+          latest-version: ${{ github.event.release.tag_name }}
+          release-notes: ${{ github.event.release.body }}
+
+      - name: Update Docs Changelog
+        run: |
+          # Get current date in the required format
+          CURRENT_DATE=$(date +"%Y‑%m‑%d")
+
+          # Create the new changelog entry
+          NEW_ENTRY="<Update label=\"$CURRENT_DATE\">
+            ## ${{ github.event.release.tag_name }}
+            ${{ github.event.release.body }}
+          </Update>
+
+          "
+
+          # Read the current changelog and insert the new entry after the front matter
+          python -c "
+          import re
+
+          # Read the current changelog
+          with open('docs/changelog.mdx', 'r') as f:
+              content = f.read()
+
+          # Find the end of the front matter
+          front_matter_end = content.find('---', content.find('---') + 1) + 3
+
+          # Split content into front matter and body
+          front_matter = content[:front_matter_end]
+          body = content[front_matter_end:]
+
+          # Create new entry
+          new_entry = '''$NEW_ENTRY'''
+
+          # Combine and write back
+          new_content = front_matter + '\n\n' + new_entry + body.lstrip()
+
+          with open('docs/changelog.mdx', 'w') as f:
+              f.write(new_content)
+          "
+
+      - name: Commit updated CHANGELOG
+        uses: stefanzweifel/git-auto-commit-action@v5
+        with:
+          branch: ${{ github.event.release.target_commitish }}
+          commit_message: Update CHANGELOG and docs changelog
+          file_pattern: CHANGELOG.md docs/changelog.mdx

mcp_use-1.3.3/.github/workflows/claude.yml

@@ -0,0 +1,36 @@
+name: Claude PR Assistant
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude-code-action:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+      (github.event_name == 'issues' && contains(github.event.issue.body, '@claude'))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude PR Action
+        uses: anthropics/claude-code-action@beta
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          timeout_minutes: "60"

{mcp_use-1.3.1 → mcp_use-1.3.3}/.github/workflows/publish.yml

@@ -2,9 +2,8 @@ name: Release
 
 on:
   workflow_run:
-    workflows: ["Python Tests"]
-    branches:
-      - main
+    workflows: ["Python Tests", "Transports"]
+    branches: [main]
     types:
       - completed
 
@@ -15,9 +14,8 @@ permissions:
 
 jobs:
   check-version-and-publish:
-    # Only proceed if the referenced workflow completed successfully
-    if: ${{ github.event.workflow_run.conclusion == 'success' }}
     runs-on: ubuntu-latest
+    if: ${{ github.event.workflow_run.conclusion == 'success' }}
     steps:
       - uses: actions/checkout@v3
         with:
@@ -72,58 +70,8 @@ jobs:
           name: Release v${{ steps.check-version.outputs.new_version }}
           draft: false
           prerelease: false
-          generateReleaseNotes: true
-
-      - name: Update Docs Changelog
-        if: steps.check-version.outputs.is_new_version == 'true'
-        run: |
-          # Get the release notes from the created release
-          RELEASE_NOTES=$(gh release view v${{ steps.check-version.outputs.new_version }} --json body --jq '.body')
-
-          # Get current date in the required format
-          CURRENT_DATE=$(date +"%Y‑%m‑%d")
-
-          # Create the new changelog entry
-          NEW_ENTRY="<Update label=\"$CURRENT_DATE\">
-            ## v${{ steps.check-version.outputs.new_version }}
-            $RELEASE_NOTES
-          </Update>
-
-          "
-
-          # Read the current changelog and insert the new entry after the front matter
-          python -c "
-          import re
-
-          # Read the current changelog
-          with open('docs/changelog.mdx', 'r') as f:
-              content = f.read()
-
-          # Find the end of the front matter
-          front_matter_end = content.find('---', content.find('---') + 1) + 3
-
-          # Split content into front matter and body
-          front_matter = content[:front_matter_end]
-          body = content[front_matter_end:]
-
-          # Create new entry
-          new_entry = '''$NEW_ENTRY'''
-
-          # Combine and write back
-          new_content = front_matter + '\n\n' + new_entry + body.lstrip()
-
-          with open('docs/changelog.mdx', 'w') as f:
-              f.write(new_content)
-          "
-
-          # Commit and push the updated changelog
-          git config --local user.email "action@github.com"
-          git config --local user.name "GitHub Action"
-          git add docs/changelog.mdx
-          git commit -m "docs: update changelog for v${{ steps.check-version.outputs.new_version }}" || echo "No changes to commit"
-          git push || echo "No changes to push"
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          generateReleaseNotes: false
+          omitBodyDuringUpdate: true
 
       - name: Publish to PyPI
         if: steps.check-version.outputs.is_new_version == 'true'

mcp_use-1.3.3/.github/workflows/release-drafter.yml

@@ -0,0 +1,41 @@
+name: Release Drafter
+
+on:
+  push:
+    branches:
+      - main
+
+  # pull_request event is required only for autolabeler
+  pull_request:
+    # Only following types are handled by the action, but one can default to all as well
+    types: [opened, reopened, synchronize]
+  # pull_request_target event is required for autolabeler to support PRs from forks
+  # pull_request_target:
+  #   types: [opened, reopened, synchronize]
+
+permissions:
+  contents: read
+
+jobs:
+  update_release_draft:
+    permissions:
+      # write permission is required to create a github release
+      contents: write
+      # write permission is required for autolabeler
+      # otherwise, read permission is required at least
+      pull-requests: write
+    runs-on: ubuntu-latest
+    steps:
+      # (Optional) GitHub Enterprise requires GHE_HOST variable set
+      #- name: Set GHE_HOST
+      #  run: |
+      #    echo "GHE_HOST=${GITHUB_SERVER_URL##https:\/\/}" >> $GITHUB_ENV
+
+      # Drafts your next Release notes as Pull Requests are merged into "master"
+      - uses: release-drafter/release-drafter@v6
+        # (Optional) specify config name to use, relative to .github/. Default: release-drafter.yml
+        # with:
+        #   config-name: my-config.yml
+        #   disable-autolabeler: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

{mcp_use-1.3.1 → mcp_use-1.3.3}/CLAUDE.md

@@ -9,7 +9,14 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 ## Development Commands
 
 ### Setup
+
 ```bash
+# Activate virtual environment (if it exists)
+source env/bin/activate
+
+# Create virtual environment if it doesn't exist
+# python -m venv env && source env/bin/activate
+
 # Install for development
 pip install -e ".[dev,search]"
 
@@ -18,6 +25,7 @@ pip install -e ".[dev,anthropic,openai,e2b,search]"
 ```
 
 ### Code Quality
+
 ```bash
 # Run linting and formatting
 ruff check --fix
@@ -31,6 +39,7 @@ pre-commit run --all-files
 ```
 
 ### Testing
+
 ```bash
 # Run all tests
 pytest
@@ -50,6 +59,7 @@ DEBUG=2 pytest tests/unit/test_client.py -v -s
 ```
 
 ### Local Development
+
 ```bash
 # Debug mode environment variable
 export DEBUG=1  # INFO level
@@ -64,23 +74,27 @@ export MCP_USE_DEBUG=2
 ### Core Components
 
 **MCPClient** (`mcp_use/client.py`)
+
 - Main entry point for MCP server management
 - Handles configuration loading from files or dictionaries
 - Manages multiple MCP server sessions
 - Supports sandboxed execution via E2B
 
 **MCPAgent** (`mcp_use/agents/mcpagent.py`)
+
 - High-level agent interface using LangChain's agent framework
 - Integrates LLMs with MCP tools
 - Supports streaming responses and conversation memory
 - Can use ServerManager for dynamic server selection
 
 **MCPSession** (`mcp_use/session.py`)
+
 - Manages individual MCP server connections
 - Handles tool discovery and resource management
 - Maintains connection state and lifecycle
 
 **Connectors** (`mcp_use/connectors/`)
+
 - Abstraction layer for different MCP transport protocols
 - `StdioConnector`: Process-based MCP servers
 - `HttpConnector`: HTTP-based MCP servers
@@ -88,6 +102,7 @@ export MCP_USE_DEBUG=2
 - `SandboxConnector`: E2B sandboxed execution
 
 **ServerManager** (`mcp_use/managers/server_manager.py`)
+
 - Provides dynamic server selection capabilities
 - Allows agents to choose appropriate servers for tasks
 - Manages server tool discovery and activation
@@ -102,24 +117,26 @@ export MCP_USE_DEBUG=2
 
 **Multi-Transport Support**: Supports stdio, HTTP, WebSocket, and sandboxed connections to MCP servers.
 
-**Telemetry**: Built-in telemetry using PostHog for usage analytics (can be disabled).
+**Telemetry**: Built-in telemetry using PostHog and Scarf.sh for usage analytics (can be disabled).
 
 ## Configuration Examples
 
 ### Basic Server Configuration
+
 ```json
 {
   "mcpServers": {
     "playwright": {
       "command": "npx",
       "args": ["@playwright/mcp@latest"],
-      "env": {"DISPLAY": ":1"}
+      "env": { "DISPLAY": ":1" }
     }
   }
 }
 ```
 
 ### HTTP Server Configuration
+
 ```json
 {
   "mcpServers": {
@@ -131,6 +148,7 @@ export MCP_USE_DEBUG=2
 ```
 
 ### Multi-Server Configuration
+
 ```json
 {
   "mcpServers": {
@@ -159,17 +177,20 @@ export MCP_USE_DEBUG=2
 ## Testing Strategy
 
 ### Unit Tests (`tests/unit/`)
+
 - Test individual components in isolation
 - Mock external dependencies
 - Focus on business logic and edge cases
 
 ### Integration Tests (`tests/integration/`)
+
 - Test component interactions
 - Include real MCP server integrations
 - Organized by transport type (stdio, sse, websocket, etc.)
 - Custom test servers in `tests/integration/servers_for_testing/`
 
 ### Test Configuration
+
 - Uses pytest with asyncio mode
 - Fixtures defined in `conftest.py`
 - Test servers provide controlled MCP environments
@@ -187,18 +208,21 @@ export MCP_USE_DEBUG=2
 ## Common Development Tasks
 
 ### Adding a New Connector
+
 1. Extend `BaseConnector` in `mcp_use/connectors/`
 2. Implement required async methods
 3. Add connector to factory in `config.py`
 4. Write integration tests
 
 ### Adding New Agent Features
+
 1. Modify `MCPAgent` class in `mcp_use/agents/mcpagent.py`
 2. Update system prompt templates if needed
 3. Add comprehensive tests
 4. Update documentation
 
 ### Testing with Custom MCP Servers
+
 1. Create test server in `tests/integration/servers_for_testing/`
 2. Add integration test in appropriate transport directory
 3. Use custom servers for controlled testing scenarios

mcp_use-1.3.3/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+dev@mcp-use.io.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

{mcp_use-1.3.1 → mcp_use-1.3.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcp-use
-Version: 1.3.1
+Version: 1.3.3
 Summary: MCP Library for LLMs
 Author-email: Pietro Zullo <pietro.zullo@gmail.com>
 License: MIT
@@ -15,6 +15,9 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: >=3.11
 Requires-Dist: aiohttp>=3.9.0
+Requires-Dist: anyio>=4.0.0
+Requires-Dist: authlib>=1.5.2
+Requires-Dist: httpx>=0.28.1
 Requires-Dist: jsonschema-pydantic>=0.1.0
 Requires-Dist: langchain-community>=0.0.10
 Requires-Dist: langchain>=0.1.0
@@ -22,13 +25,17 @@ Requires-Dist: mcp>=1.9.3
 Requires-Dist: posthog>=4.8.0
 Requires-Dist: pydantic>=2.0.0
 Requires-Dist: python-dotenv>=1.0.0
+Requires-Dist: scarf-sdk>=0.1.0
+Requires-Dist: starlette>=0.41.0
 Requires-Dist: typing-extensions>=4.8.0
+Requires-Dist: uvicorn>=0.32.0
 Requires-Dist: websockets>=12.0
 Provides-Extra: anthropic
-Requires-Dist: anthropic>=0.15.0; extra == 'anthropic'
+Requires-Dist: langchain-anthropic; extra == 'anthropic'
 Provides-Extra: dev
 Requires-Dist: black>=23.9.0; extra == 'dev'
-Requires-Dist: fastmcp; extra == 'dev'
+Requires-Dist: fastapi; extra == 'dev'
+Requires-Dist: fastmcp==2.8.0; extra == 'dev'
 Requires-Dist: isort>=5.12.0; extra == 'dev'
 Requires-Dist: mypy>=1.5.0; extra == 'dev'
 Requires-Dist: pytest-asyncio>=0.21.0; extra == 'dev'
@@ -38,7 +45,7 @@ Requires-Dist: ruff>=0.1.0; extra == 'dev'
 Provides-Extra: e2b
 Requires-Dist: e2b-code-interpreter>=1.5.0; extra == 'e2b'
 Provides-Extra: openai
-Requires-Dist: openai>=1.10.0; extra == 'openai'
+Requires-Dist: langchain-openai; extra == 'openai'
 Provides-Extra: search
 Requires-Dist: fastembed>=0.0.1; extra == 'search'
 Description-Content-Type: text/markdown
@@ -76,7 +83,7 @@ Description-Content-Type: text/markdown
     <a href="https://x.com/pederzh" alt="Twitter Follow - Luigi">
         <img src="https://img.shields.io/twitter/follow/Luigi?style=social" /></a>
     <a href="https://discord.gg/XkNkSkMz3V" alt="Discord">
-        <img src="https://dcbadge.limes.pink/api/server/https://discord.gg/XkNkSkMz3V?style=flat" /></a>
+        <img src="https://dcbadge.limes.pink/api/server/XkNkSkMz3V?style=flat" /></a>
 </p>
 🌐 MCP-Use is the open source way to connect **any LLM to any MCP server** and build custom agents that have tool access, without using closed source or application clients.
 

{mcp_use-1.3.1 → mcp_use-1.3.3}/README.md

@@ -31,7 +31,7 @@
     <a href="https://x.com/pederzh" alt="Twitter Follow - Luigi">
         <img src="https://img.shields.io/twitter/follow/Luigi?style=social" /></a>
     <a href="https://discord.gg/XkNkSkMz3V" alt="Discord">
-        <img src="https://dcbadge.limes.pink/api/server/https://discord.gg/XkNkSkMz3V?style=flat" /></a>
+        <img src="https://dcbadge.limes.pink/api/server/XkNkSkMz3V?style=flat" /></a>
 </p>
 🌐 MCP-Use is the open source way to connect **any LLM to any MCP server** and build custom agents that have tool access, without using closed source or application clients.