Skip to main content
Glama

encode_manage_credentials

Store, check, or remove ENCODE API credentials for accessing restricted or unreleased genomic data. Credentials are securely stored in your operating system's keyring.

Instructions

Manage ENCODE API credentials for accessing restricted/unreleased data.

Most ENCODE data is public and requires no authentication. Credentials are only needed for unreleased or restricted datasets.

Credentials are stored securely in your OS keyring (macOS Keychain, Linux Secret Service, Windows Credential Locker) and never in plaintext.

WHEN TO USE: Use only for accessing unreleased/restricted ENCODE data. Public data requires no authentication. RELATED TOOLS: encode_search_experiments

Args: action: What to do: - "store": Save new credentials (requires access_key and secret_key) - "check": Check if credentials are configured - "clear": Remove stored credentials access_key: Your ENCODE access key (only for action="store") secret_key: Your ENCODE secret key (only for action="store")

Returns: JSON with action result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
access_keyNo
secret_keyNo

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ammawla/encode-toolkit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server