Bestie MCP
MCP server for semantic search over Logseq journal entries, backed by PGVector and Amazon Bedrock embeddings.
Requirements
- Python 3.11+
- PostgreSQL with the
pgvectorextension - AWS credentials with Bedrock access (Titan Embed v2 + Claude)
Setup
pip install -e .
cp .env.example .env # edit with your values
Environment variables:
| Variable | Default | Description |
|---|---|---|
PGVECTOR_DB_URL |
postgresql+psycopg://postgres:postgres@localhost:5432/postgres |
Postgres connection string |
BEDROCK_AWS_PROFILE |
— | AWS profile name (takes precedence over key/secret) |
BEDROCK_IAM_ACCESS_KEY |
— | AWS access key ID |
BEDROCK_IAM_SECRET_KEY |
— | AWS secret access key |
Transports
Streamable HTTP (recommended — for LibreChat, Claude Code, remote use)
The server runs on port 9999 by default and exposes the MCP endpoint at /mcp.
# direct
python -m logseq_mcp.main
# with options
python -m logseq_mcp.main --host 0.0.0.0 --port 9999
# via env var
MCP_TRANSPORT=http python -m logseq_mcp.main
Claude Code — add to .mcp.json in your project root:
{
"mcpServers": {
"logseq": {
"type": "http",
"url": "http://localhost:9999/mcp"
}
}
}
LibreChat — add to librechat.yaml:
mcpServers:
logseq:
type: streamable-http
url: http://localhost:9999/mcp
stdio (for local Claude Desktop / CLI use)
python -m logseq_mcp.main --transport stdio
# via env var
MCP_TRANSPORT=stdio python -m logseq_mcp.main
Claude Code — add to .mcp.json:
{
"mcpServers": {
"logseq": {
"type": "stdio",
"command": "python",
"args": ["-m", "logseq_mcp.main", "--transport", "stdio"],
"env": {
"PGVECTOR_DB_URL": "postgresql+psycopg://postgres:postgres@localhost:5432/postgres",
"BEDROCK_AWS_PROFILE": "your-profile"
}
}
}
}
Docker
Runs streamable HTTP on port 9999 via gunicorn + UvicornWorker (4 workers by default).
docker build -t logseq-mcp .
docker run -p 9999:9999 \
-e PGVECTOR_DB_URL=postgresql+psycopg://user:pass@host:5432/db \
-e BEDROCK_IAM_ACCESS_KEY=... \
-e BEDROCK_IAM_SECRET_KEY=... \
logseq-mcp
To tune the worker count:
docker run -p 9999:9999 ... logseq-mcp \
gunicorn logseq_mcp.main:app \
--worker-class uvicorn.workers.UvicornWorker \
--workers 2 \
--bind 0.0.0.0:9999
Health check: GET /health
Tools
search_journal_entries
Semantic search over Logseq journal entries using vector similarity.
Metadata
Release files for logseq-2-mcp 0.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| logseq_2_mcp-0.7.1.tar.gz | 16.9 kB | Without provenance | Details for logseq_2_mcp-0.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| logseq_2_mcp-0.7.1-py3-none-any.whl | Python 3 | none | any | Details for logseq_2_mcp-0.7.1-py3-none-any.whl |
Total release size: 37.6 kB
Release files / logseq_2_mcp-0.7.1.tar.gz
| Download URL | logseq_2_mcp-0.7.1.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a59ebbcbf7e0a7bf0b33befe9b37232fe28e0966f3b7e69ffb091af20d67011
|
|
BLAKE2b-256 checksum How to use checksums |
6bf5b72bc5d747a3c73158d293f04a8706f179c90f02a9a0c205328f362e79b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / logseq_2_mcp-0.7.1-py3-none-any.whl
| Download URL | logseq_2_mcp-0.7.1-py3-none-any.whl |
|---|---|
| Size | 20.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4a9c31334019513298450e976155b7cb37ec2eef38d1818fe6d1f4be2529286
|
|
BLAKE2b-256 checksum How to use checksums |
d16eb64fef0d58db2e57c30e0ac2d6840b3c842ed011decfb12ea4205985591f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for logseq-2-mcp 0.7.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.