mcp-langfuse
⚠️ PROJECT SETUP STAGE - NOT READY FOR USE
This repository is currently in the initial setup phase. The project structure, tooling, and CI/CD pipelines are being configured. No functionality has been implemented yet - this is an empty shell.
Do not use this package in production or development environments.
Follow the repository for updates on when the first functional release becomes available.
MCP server for Langfuse REST API with enhanced trace analysis tools
Installation
From Source
git clone https://github.com/CrackingShells/mcp-langfuse.git
cd mcp-langfuse
pip install -e .
From PyPI (when available)
pip install mcp-langfuse
Quick Start
import mcp_langfuse
# Add basic usage example here
Development
Setup Development Environment
# Clone the repository
git clone https://github.com/CrackingShells/mcp-langfuse.git
cd mcp-langfuse
# Install in development mode
pip install -e .
# Install Node.js dependencies for semantic release
npm install
Running Tests
# Run all tests
python -m unittest discover tests
# Run specific test file
python -m unittest tests.test_basic
Code Quality Tools
Set up automated code quality checks:
# Install development dependencies
pip install -e .[dev]
# Set up pre-commit hooks
pre-commit install
# Run all checks manually
pre-commit run --all-files
Once installed, pre-commit hooks will run automatically on every git commit to ensure code quality.
Building Documentation
Build and serve documentation locally:
# Serve documentation locally with live reload
mkdocs serve
# Build documentation for production
mkdocs build
Documentation is automatically published to ReadTheDocs when changes are pushed to the repository.
Making Commits
We use Conventional Commits for automated versioning:
# Use commitizen for guided commits
npm run commit
# Or commit manually with conventional format
git commit -m "feat: add new feature"
git commit -m "fix: resolve issue with X"
git commit -m "docs: update README"
Contributing
We welcome contributions! Please see our Contributing Guide for details on:
- Development workflow
- Code style guidelines
- Testing requirements
- Pull request process
License
This project is licensed under the GNU Affero General Public License v3 - see the LICENSE file for details.
Links
- Homepage: https://github.com/CrackingShells/mcp-langfuse
- Bug Reports: https://github.com/CrackingShells/mcp-langfuse/issues
- Documentation: https://crackingshells.github.io/mcp-langfuse/
Metadata
Release files for mcp-langfuse 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_langfuse-0.1.0.tar.gz | 375.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_langfuse-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 786.6 kB
Release files / mcp_langfuse-0.1.0.tar.gz
| Download URL | mcp_langfuse-0.1.0.tar.gz |
|---|---|
| Size | 375.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3a7cd351b0eca91ea1965db3d5a46427ff11cf4cf7847e3ff0931da13a9495b
|
|
BLAKE2b-256 checksum How to use checksums |
f1d663c73e15afc27bcec30b203ed3be2c1e8245dec4b046ada810d344490981
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 2, 2025.
Transparency logRelease files / mcp_langfuse-0.1.0-py3-none-any.whl
| Download URL | mcp_langfuse-0.1.0-py3-none-any.whl |
|---|---|
| Size | 410.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
454180dadd042e260abcdf6b8009a3803d0a9823f8d5882e540bef1549650a2e
|
|
BLAKE2b-256 checksum How to use checksums |
83b385d005db508f73548788ca3447466bc7f6b6ecc1c20821c1b1af2e615899
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 2, 2025.
Transparency log